It’s important to be able to look at the entirety of your application architecture, not just specific aspects of it, and understand how different parts connect. Observability comes first, followed by monitoring. In this post, we’ll dive into the database part of your architecture to show how you can monitor and optimize your database performance.

Anyone who is responsible for database performance knows how demanding and challenging database performance tuning is when managing a database. One of the critical functions of this process – database monitoring – is often overlooked. Database monitoring includes identifying the right SQL for tuning, determining right way to tune and whether SQL is right thing to tune.

Redis is an open-source in-memory data store. You can use Redis as a database, message broker, or cache. It also supports Lua script evaluation so you can build automation scripts or custom operations on top of your key-value Redis store. Typically, developers use language-specific client libraries when building apps with Redis. These clients abstract Redis’ command-line interface (CLI), making it easier to work with but more work to set up.

NoSQL is a database management system that exists as an antithesis to SQL, in that it doesn’t store data in a relational model. As such, data can essentially be stored as anything, in any way a developer chooses, within reason of course. This flexibility comes from the fact that NoSQL doesn’t require a schema in the same way that SQL does.