2 ms·
This is interesting to me because my company is right in the middle of the serverless movement. I know and work with over a dozen large companies that have move
by fugazithehaxoar 8y ago
This is interesting to me because my company is right in the middle of the serverless movement. I know and work with over a dozen large companies that have moved their fairly standard micoservice-oriented architecture over to 100% serverless. Lots of people in the ops world still think this is some kind of marketing nonsense or black magic though.
Long story short, when engineering teams move to serverless, they get huge scalability benefits and essentially "squashing their stack" making team engineering velocity way faster than when they were using EC2/Kubernetes/VMs.
Imagine 10 years ago, being a LAMP stack developer. One day, you find a hosting platform lat allows you to be a much more fast/effective LAMP developer while only needing to work with M+P. This is the core benefit of serverless.
Yes, there are servers under the hood somewhere at an AWS datacenter. Yes, infrastructure still gets patched, updated, etc. Serverless is all about letting engineering team focus on building the application and making the infrastructure "not my problem".
- closeparen 8y agoIMO Google Cloud correctly describes its serverless platform as a place to host little one-off utilities in your infrastructure that don’t need to consume resources all the time. (Employee onboarding, deployment plumbing, etc). Not as an appropriate way to build your entire product. If you’re using it that way, it’s really no different from Elastic Beanstalk / Heroku / ye olde shared PHP hosting. Which is fine, but not some kind of revolution. Just the pendulum swinging back.