Member-only story
Too juicy to resist! 🤣
This is what happens when we stop thinking and relegate that job to <insert anything/ anyone here>. It’s like hiring a contractor to build your house. Back where I came from, if you need it done, you got to be onsite and supervise it is actually happening. Otherwise, the results are completely different from the plans! Expats learn this lesson too late.
Reminds me of the time I designed something from scratch for a company and compared it with a design pattern and we found a major issue with the design pattern. That is when I learned design patterns can have “known bugs” too!
There are some things that many people don’t know about serverless. I can speak to my experience from Azure:
- There is no cap on the cost with serverless. Azure has some options today which solve that problem. A bug causing cash burn is a nightmare scenario!
- If you are willing to do extra work, you can save a ton on a non-serverless system like Service Fabric (similar to Kubernetes) where you can keep the VMs as small as your application requires.
- With some more work (on Service Fabric), you can add a different node type that is larger, only for the specific customers which require a larger compute/ memory/ disk i/o or network requirement. This is super cost-effective (small by…
