Hacker News Reader

Comment by TimTheTinker | Hacker News Reader

I’m curious what your take is on the JAMStack+lambdas style of app development.

I am working on a new web app. Initially, Elixir/Phoenix was looking like an excellent option, but then I looked at hosting and decided it would be easier to use something like the Serverless framework for AWS deployment which JAMstack+lambdas seems to match better — no need to manage VMs and networking infrastructure, mostly.

View on HN

JAMstack is...not my jam.

I'm a big fan of rendering majority on a server and then shipping it, especially with Phoenix's LiveView which allows you to write reactive UI without writing Javascript.

But I said it in another comment: shipping value beats everything. If you can ship quickly and effectively in JAMstack to lambda, don't let anyone tell you that's wrong.

Shipping value is important. If you can build a solution faster in a monolithic, MVC style framework running on EC2 instances, then do that. I think people get too bogged down in the minutiae up front and forget they are being paid to solve a problem ASAP. Worry about optimisations and improvements when its going to add more value than right up front when the burning need of the business is to have something - ANYTHING - up and running and helping generate revenue.

I have been building JAMstack apps since 2016 using exactly the stack you are asking about. Using something like the Serverless Framework to help you build and deploy your collection of microservice backends into AWS as well as your static frontend into S3 is just awesome to behold. I have had an app running for 3 years with spikes of traffic and have never had to worry about maintenance or downtime.

Reply on news.ycombinator.com