Why is this channel so allergic to deploying any non-serverless resources? You guys went through this massive gauntlet of different complex, expensive architecture solutions but didn't even mention the cheapest and most logical option - a single EC2 instance in a private subnet! Company employees don't scale exponentially and even if they did, most companies don't have more than a few thousand employees at most. A single EC2 instance could easily serve a static site stored on S3 with practically no hastle. It takes 5 minutes to deploy an ami with nginx pre-installed. Why are you over complicating this so much?
No allergies here! We always try to talk through the trade-offs with serverless and alternatives. We have seen single person projects succeed very well with serverless and the same for EC2. We have also seen the pitfalls of many options. The right choice always depends on the context. Setup time alone is not the only factor. In either case, consider the maintenance and ongoing development time. In this episode, we are talking about enterprise applications. A single instance with few security guardrails and no high availability considerations is not going to fit for most companies in the category.
A great discussion guys. I really liked the no BS approach, pure gold and focused conversation
Thanks Sagar. We really appreciate the comment.
Can amplify be an option? What are the limitations there?
Why is this channel so allergic to deploying any non-serverless resources? You guys went through this massive gauntlet of different complex, expensive architecture solutions but didn't even mention the cheapest and most logical option - a single EC2 instance in a private subnet! Company employees don't scale exponentially and even if they did, most companies don't have more than a few thousand employees at most. A single EC2 instance could easily serve a static site stored on S3 with practically no hastle. It takes 5 minutes to deploy an ami with nginx pre-installed. Why are you over complicating this so much?
No allergies here! We always try to talk through the trade-offs with serverless and alternatives. We have seen single person projects succeed very well with serverless and the same for EC2. We have also seen the pitfalls of many options. The right choice always depends on the context. Setup time alone is not the only factor. In either case, consider the maintenance and ongoing development time.
In this episode, we are talking about enterprise applications. A single instance with few security guardrails and no high availability considerations is not going to fit for most companies in the category.