Submit to your local DSC chapter CFPSubmit now!
close

DSC Australia

Database Guardrails – new age for developers and databases

with Adam Furmanek
play_circle

Description:

You can’t deploy blindly and let your application fail. You need to prevent the bad code from reaching production, monitor your databases, and automatically troubleshoot when something is wrong. You need database guardrails, and you need them now.

The typical test suite is not enough to capture all the issues around databases. Tests do not capture long migrations, wrong configurations, slow queries that don’t scale. Load tests may capture some of them, but are far too late and too expensive. We need a new approach to our SDLC, we need to integrate database guardrails into our process as early as possible.

In this talk we are going to see how to use OpenTelemetry to improve the whole SDLC. We’ll learn how to validate our data access queries will scale, our database will not go down during the deployment, and how to automatically root cause issues across all layers of the tech stack.

Key takeaways 

  • Improving SDLC with database guardrails
  • Using OpenTelemetry in real world 
  • Getting automated observability and troubleshooting for all data access layer

 

Join the Community!

If you haven’t joined the Discord community, please do so! You can find us on Discord at: https://devseccon.io/discordcommunity

Tags:

Automated Observability
Data Access Optimization
Database Guardrails
OpenTelemetry
SDLC Improvement

Adam Furmanek

DevRel at Metis

About Adam Furmanek

I am Adam Furmanek, and I am a professional software engineer with over a decade of experience. In my career, I worked with all layers of software engineering and multiple types of applications, including logistics, e-commerce, machine learning, data analysis, and database management. I am always interested in digging deeper, exploring machine code, and going through implementation details to better understand the internals of the technologies I use every day. That’s why I like debugging, decompiling and disassembling the code to understand memory models, concurrency problems and other details hidden deeply inside.

We use cookies to ensure you get the best experience on our website.Read Privacy Policy
close