| > In November 2014 AWS Lambda was released and it was nothing short than a revolution. still not good enough to be reliable in production, more expensive than running on micro instance or digitalocean. Lambda needs a serious makeover soon or it risks developer abandonment. It's great to lock yourself in with a cloud provider. That's the only serious benefit you get. You still need to figure out how to scale properly, getting on AWS helps but it's not a plug and play scalable thing. I've largely abandoned development on Lambda because you have to upload your code every time which is annoying. Not only that, they randomly take 5~10 seconds to respond. Also unhelpful are service error messages with no explanation or help from discussion boards. I was told to purchase their support license. So it seems like AWS is locking in developers and companies with a non user friendly documentation and arcane hidden pitfalls then leaving them no choice but to purchase support since the cost is cheap (pay to play right?) until you add up the effort of integrating with AWS and the cost of lock-in.... AWS lambda is great for prototyping but it doesn't have the tools or a proper development guideline to utilize it. There doesn't seem to be much enthusiasm from AWS either, and if they pull the plug, well hope you didn't build any mission critical apps on lambda backends because you are going to have some considerable downtime. |