Readit NewsThat said, Lambda has been out for a while and seems to have avoided taking over the world. Generic vCPU-hours are so cheap now though that it isn't compelling from a a cost perspective (serverless will either cost you more at the high end of the scale, or else save you a few bucks a month on your idle instances at the low end). Also, the developer experience isn't as good yet IMO. Thinks like LocalStack help, but it's still not natural-feeling to deploy a big application this way. (scale-to-zero it's great for small side projects though -- I have a few apps in Cloud Run that cost me like a nickel a month, a few dollars if I have a good month in terms of traffic).
I do not know if this is solvable: a permanent service with light autoscaling handles even inconsistent load so well and reduces operational complexity so much that I don't know if serverless will be anything more than toys. It is no coincidence that AWS Lambda's first language was a frontend language* (Node.js). Those use cases have low to moderate scale (because after that you split frontend and backend).
^Amazon Prime Video post: https://www.primevideotech.com/video-streaming/scaling-up-th.... *First mention of AWS Lambda languages in AWS Compute Blog only mentioned nodejs: https://aws.amazon.com/blogs/compute/container-reuse-in-lamb...
- Apache Spark starts its relatively slow decline in favor of vendor and in-house solutions.
- Cost drives cloud systems away from managed solutions (think AWS Batch) towards semi-managed solutions (think self-run k8s deployments but on AWS EKS).
- There are no improvements in autoscaling k8s clusters.
- Integration testing is replaced by testing in the development environment.
- Saudi Arabia will release an ethical standards requirement for each of its Western tech company holdings. The exact definition will be confusingly progressive, which will put everyone on guard.
Just because there are competitors doesn’t mean there’s no room for you.
Don’t look for reasons not to give it a shot.
Don’t tell anyone about it. There’s a lot of psychology trickery going on when you share your idea with people. Either they shit on the idea and you lose incentive to work on it, or the praise you and your brain takes that dopamine rush and considers the job over. Don’t tell anyone, just get to work.
I do think you're right about tech. Try it yourself, build it out, have some fun, be a dork. Then tell people.
For my project, I was building some tools that were helping me understand the problem space (which was new to me and that he fundamentally did not understand himself). In a team stand-up, which included the CTO, I shared that I had built a useful tool that was helping me and he chimes in: "I think that you just spend all of your time making tools and don't do any real work." Even if there was a conversation to be had about how I was spending my time, it was ridiculous that he was bringing this up for the first time not 1:1 but with the whole group. I resigned a few days after that interaction (which was probably at least the fourth or fifth time he'd pulled something similar in the two months I worked with them). BTW, he would never just say "you are a moron" but it was very clearly the subtext of almost all of the feedback he gave, except to the most junior people who didn't threaten him in any way.