I think with any technology, the more pieces, the more complexity you have. In a way, serverless is a form of microservice.
Personally, I love the idea of FaaS/serverless. But it can add so many points of failure that you end up creating more work than necessary for an MVP.
In general, find the right tool for the job. Some will be functions on Webtask (a personal favorite of mine), Azure or AWS, some of it will be an app in Ruby.
True serverless technology due to the microservice architecture can add complexity to the application.
The granularity of each microservice plays a huge role. Small numerous functions are difficult to handle and I can't code a function which has execution time more than 5 minutes (for AWS Lambda).
I think with any technology, the more pieces, the more complexity you have. In a way, serverless is a form of microservice.
Personally, I love the idea of FaaS/serverless. But it can add so many points of failure that you end up creating more work than necessary for an MVP.
In general, find the right tool for the job. Some will be functions on Webtask (a personal favorite of mine), Azure or AWS, some of it will be an app in Ruby.
True serverless technology due to the microservice architecture can add complexity to the application.
The granularity of each microservice plays a huge role. Small numerous functions are difficult to handle and I can't code a function which has execution time more than 5 minutes (for AWS Lambda).
A little more on webtask.io - if you have javascript developers, you can very quickly try out some functions there for MVPs.
It is really easy to use, and the free tier is quite functional for experimentation.
Webtask looks really cool! (I wish I could have come to that conclusion a bit faster. Their landing page is vague)
Incredibly low-key. Fun to use and setup is fast.