Simplifying Microservices Debugging with Thundra Sidekick – Security Boulevard



We’ll make sure to share the best materials crafted for you!

4 minutes read

Berkay Mollamustafaoglu

Written by Berkay Mollamustafaoglu

Co-founder and CEO @Thundra


I’m one of the fortunate people who have witnessed the (r)evolution of software development and delivery throughout my career. From programs deployed in local racks to serverless running with the pay-as-you-go paradigm, we’ve seen a breakthrough in computing in a relatively short time.

I’ve been part of the modernization of Operations team members along with the emergence of the DevOps paradigm and “modern” applications. Due to these changes, applications are now much more distributed and increasingly built using services provided by cloud services (DynamoDB, SQS, etc.), other vendors (Twilio, Stripe, etc.), or other teams in the same organization. However, these changes introduced new challenges for developers and many new failures that can be hard to understand and resolve.

For years, the industry has been investing heavily in developing tooling to resolve issues in such complex applications. At my previous startup, OpsGenie, we focused on making the life of on-call folks a little easier. As we start our incident management journey