I'm looking for advice as we transition our multi-tenant e-commerce app, built on Laravel and hosted on Vapor (using Lambda), to production soon. We're using Aurora Serverless v2 for our database, but I'm stuck deciding between serverless Redis and a fixed Redis instance. Redis will handle session storage, caching, queues, and rate limiting for us. Since our old application had unpredictable traffic spikes—especially during large product launches and new merch drops—I'm unsure which Redis setup would be best for performance and reliability. I'd appreciate any tips on what factors to consider. Cost isn't a major concern; we just want the best performance and reliability.
2 Answers
If you can predict your traffic patterns fairly well, I'd recommend going with a fixed Redis instance. It tends to offer more consistent performance, especially when you're managing unpredictable spikes in traffic. If your situation changes, you can always adapt later.
Consider your priorities—do you prefer to save on costs or invest your time into managing infrastructure? Serverless options can save you time, but they might be more costly in the long run if you need to scale significantly. For your use case, with 24/7 monitoring included, either could work well, but performance might be more reliable with a fixed instance.
Since we’re okay with monitoring and maintenance, I'm just looking for the best technical fit. I totally see the value in starting with a fixed instance. If we find it lacks later, switching isn't impossible.
I get that, but my scenario is a bit tricky. We're transitioning from an old app, and clients will migrate slowly to the new platform, so I can't predict the exact traffic just yet. I'm leaning towards serverless for flexibility.