6 ms·
I couldn't disagree with this article more. We've built an entire architecture running our Series A startup on serverless technologies, and it's been fantastica
by hn_throwaway_99 5y ago
I couldn't disagree with this article more. We've built an entire architecture running our Series A startup on serverless technologies, and it's been fantastically successful. We have a small team, so I specifically knew I didn't have the team capacity to do a lot of server management. Here are our general components:
1. We have a bunch of services running on App Engine NodeJS Flexible version. We have extremely minimal lock-in because we basically just have a normal Express app serving GraphQL.
2. In fact, we migrated some of our services to Cloud Run for lower costs. Cloud Run is basically serverless Docker containers, and the migration was very easy. Again, our apps are for the most part platform agnostic apps on Node.
3. We also make use of Google Cloud Functions for our asynchronous event handling. This has also been a great choice.
Going with serverless tech has easily saved us ~2 FTEs in a team of fewer than 10 engineers.
- _huayra_ 5y agoHow portable is an app using serverless? With VMs (and especially containers / k8s stuff), you can just pick up the whole app and ship it off to another cloud provider (except if one uses custom offerings). Can serverless functions be done the same way? I guess at the end of the day it's just JS / Python code, but is there an "export to / import from a common format" API / web portal button?
- rmbyrro 5y agoIt depends on how you develop. In most cases, it's arguably easy to separate your code from cloud-specific stuff. If you do that, you have high portability.
- potatoman22 5y agoPortability is nice, but is it really needed all that often?
- fartcannon 5y agoYes, because Amazon, like a bad landlord, could at any point in time kick you out, or quintuple your rent. What GP has built is fragile.
- jakelazaroff 5y agoGP said it’s just an Express app, right? That should be pretty easy to run anywhere.
- hn_throwaway_99 5y ago"Serverless" can mean many things: * Cloud Run is just running a Docker image. It's basically as platform agnostic as Docker is. * Similarly, App Engine Flexible is just running a plain version of NodeJS. No specific lockin if you don't access GCP-specific services. * With respect to Google Cloud Functions, again we're just running a simple Node service in response to some PubSub events. There would be work to migrate this, for example, to AWS Lambda, but it would be a very straightforward mapping.
- Ozzie_osman 5y agoHow many services? I've run a pretty similar stack on Heroku with very minimal pain. It was really cheap until we started to hit some heavier scale, at which point, one engineer became part-time devops (like 30%) and we moved to AWS.
- DangitBobby 5y agoI was going to mention CloudRun as a specific counterpoint to the author's opinion on serverless functions. It can't get much more portable than a container running on arbitrary HTTP triggers. We use pub/sub as a trigger because we like the functionality but you can do whatever you want. You can, for example, containerize your monolith and expose task triggers via API endpoints so your web server doesn't have to do that work. I really like it.
- matchagaucho 5y agoThe article's premise is actually about "vendor lock-in"; which is hiding behind a click-bait title. We similarly run a start-up on AWS serverless, and there are zero regrets. The portion of code that actually interacts with the Lambda-specific JSON requests is trivial, and just routes to code that is unaware of environment.
- aenis 5y ago+1 for Cloud Run. I run a few production workloads with it, and its dirt cheap and reliable. It has come a long way over the last two years. As for lock in: we habitually put abstractions between things like key-value stores, messaging and queuing services and the business logic -- so moving this stuff to, say, fargate/dynamo/sns/sqs would not be a lot of work -- probably a few weeks to rework the terraform scripts, figure out a good approach to roles, and thats it.
- thraxil 5y agoYeah, honestly even the Standard environment is pretty minimal in terms of lock-in. We deploy Django apps to GAE Standard with Cloud SQL and aside from a few bits in settings.py, there's nothing App Engine specific about it. I can package them up as docker apps and with a different settings file, run them pretty much anywhere else.