With serverless, there are now fewer things to be scared of while maintaining always-on software thanks to outsourced scalability, availability, and security issues. At the same time, developers tend to architect more distributed systems in order to take advantage of serverless and guarantee the modularity of their architecture. The downside of this is that losing access to the underlying server makes debugging harder than ever because you can’t pause the execution to debug. Similarly, troubleshooting serverless incidents can be a daunting task because of the asynchronous and distributed nature of serverless.
In this webinar, we'll walk through:
Why debugging is the biggest problem of serverless and existing solutions that can help you cope with this problem.
How can the online debugging solution make debuging AWS Lambda possible while it’s running on the cloud?
Understanding the root cause of incidents in distributed event-driven architecture.
Understanding the business impact of incidents.
Troubleshooting and responding to incidents both solo and as a team with distributed tracing and offline debugging together.