I'm managing a Laravel application with about 1,000 users, although not all access it at the same time—typically, I see around 20 to 100 active users concurrently. The application is fairly complex, particularly with its dynamic PDF generation feature. Currently, I'm using AWS for infrastructure, including EC2, S3, and RDS with MySQL.
Given this setup, should I go with Kubernetes or just stick to EC2 instances? I'm trying to figure out if Kubernetes might be overkill for what I need or if it's essential for my system. I have a small team of about four developers, and my main role involves quality control and tackling complex coding tasks along with major system architecture decisions.
Also, I mistakenly referred to using bare metal EC2 in my initial post, which isn't applicable here. I'm also considering ECS based on some great suggestions. What do you think?
4 Answers
If you’re just handling PDF generation and your users are sort of steady, I’d suggest looking into Fargate under ECS. It can simplify your deployment pipeline and automate scaling without you managing the underlying instances. Kubernetes can come later if you need it.
For the load you're describing, using ECS (or just EC2 with an Application Load Balancer) would be more than sufficient. Kubernetes is more suited for larger applications with a lot of microservices. Stick with what you’re comfortable with for now, and you can always pivot later if you need to scale exponentially.
Definitely, and it’s way simpler to manage. You can upgrade your EC2 instances as needed without jumping into a whole new framework.
If you're not fully settled on needing Kubernetes, you probably don’t. Generally, a simple setup with just EC2 instances, possibly behind a load balancer, can handle your user load without significant stress. Kubernetes introduces a lot more networking complexity, which might not be necessary right now. You could also explore ECS if you're looking for something that abstracts away some of that management complexity.
Exactly! For your current needs, sticking with EC2, or considering ECS, seems like a much simpler option. It gives you the scalability without the Kubernetes overhead for now.
Honestly, Kubernetes can be a bit overwhelming if your application isn't service-oriented yet. With more of a monolithic structure at the moment, starting with EC2 or even ECS would be the way to go. Converting to microservices can always come later if you find your needs changing.
Yeah, migrating to Kubernetes is much easier once you have experience under your belt. Start simple and then scale up your infrastructure when there's a real need.
That sounds like a great plan! Plus, you’re right about Kubernetes—it has its place but can add layers of complexity that may not be needed right now.