Hey Dev Community,
I am currently exploring Serverless and experimenting with it. Since it's a popular method for building applications, I would like to hear about some personal experiences with it.
- What motivated your decision to adopt Serverless architecture?
- Can you share specific functionalities or solutions that Serverless architecture enabled you to implement?
- Have you noticed any significant impact on cost efficiency due to adopting Serverless?
Feel free to share any additional thoughts or experiences beyond these questions. Your insights will be incredibly valuable to someone navigating this technology.
Top comments (2)
Serverless has always fascinated the industry, and it's being ages since when folks started using it. Martin Fowler is the main inspiration for many and including me. Here's the blog post ServerLess Architecture
Depending upon the client project or yet times based on their needs, the serverless architecture was chosen. However, there were times, we decided to fully build on serverless stack like Lambda, Elastic Bean, Elastic Container Service etc. depending upon the dedicated clients who preferred to go with the AWS. There are times, we went with the Azure Cloud too. However, it was all case by case. It's more common in the services industry to go with the suitable technologies based on the client needs.
A ton of them. Unfortunately, they are confidential and I cannot be specific in mentioning them. However, the serverless apps or services are no different from the traditional dedicated server based ones which we architect and manage.
Of course, a ton of APIs could be designed, developed and hosted with the serverless architecture. Yet time, it's not just the cost, you need to consider the scalability, performance etc. There are various factors involved in architecting and deciding on the serverless architecture. However, the cost factor is something which will be efficient with the right architecture in place. There's no silver bullet. You need to decide on what makes sense. When to choose, what type of services or application that needs to be moved to a pure serverless architecture. Remember, there's no hard and fast rule. Even AWS too failed at first and went with their CORE product with the serverless architecture, later they felt adds too much of cost and also difficult to manage, hence they went with the monolithic for that particular use-case. Please read this blog post. prime-video-audio-video-monitoring...
Thank you, @ranjancse. I have reviewed the resources you shared and they seem to be quite helpful.