Dashbird is amongst the first ones to provide a service like this but there are a few other really great ones like Epsagon.com, IOPipe.com, Thundra.io.
Now back to the question at hand:
Why is serverless the next paradigm shift in the way we create and run web services and apps?
Let me clarify, serverless is not something that AWS or Microsoft invented overnight and released back in 2015, it’s been around for way longer than that. We used to call it cloud computing and it was only available to a very select handful of individuals that had the privilege (read: $$$Money$$$) to get access to something like this. Services like AWS Lambda and MS Azure just made this idea available to the masses at a very, VERY, low price.
The biggest hurdle (or paradigm shift) we developers have to overcome is the adapting to the new way we think about the infrastructure. It’s more like a “plug and play” experience where we “plug” the code and it just runs.
We also have to get used to the little quirks that we now have to deal with like the monitoring and observability solutions.
We also need to stop with the “vendor lock-in syndrome” because this isn’t really an issue. Using platforms like Serverless you can deploy your code on any provider you choose with a couple of command lines. You’ll never have to be stuck using just one service provider.
See this article on how the two architectures stack up to get a better view of the differences between them.
Hope this little rant will shed some light on this particular subject but I’d love to hear your thoughts on this, either leave a comment or email me at email@example.com to get in touch.
Failure detection, analytics and visibility for serverless applications in under 5 minutes.