Re-evaluate serverless architecture
Spent some more time carefully considering both sides and have decided to move away from Trivl being serverless.
Here are my reasons...
- Serverless comes at the cost of portability so with Trivl being open source, it would be harder to contribute to.
- I am not prepared to sacrifice UX to save money.
I have been playing around with Digital Ocean's app platform which gives us the reduced complexity without some of the restrictions imposed on Serverless.
Here are my reasons...
- Serverless comes at the cost of portability so with Trivl being open source, it would be harder to contribute to.
- I am not prepared to sacrifice UX to save money.
I have been playing around with Digital Ocean's app platform which gives us the reduced complexity without some of the restrictions imposed on Serverless.
nice! I'm also still learning about serverless architecture and from what I found that serverless is mostly inefficient for small-medium teams. Thumbs up for actually considering the pros & cons and not merely following the trends
Nathaniel Blackburn
Author
@AbdurrahmanShofyAdianto Thanks, it's easy to get swept away in the hype but in doing so become blind to the parts people aren't talking about. Only by experiencing it yourself will you properly understand it and the opinions others have.
Please sign in to leave a comment.