Fundamentally, your database availability matters more than anything else at the moment for your SLO. So it is important to understand what keeps the DB team fr

Fundamentally, your database availability matters more than anything else at the moment for your SLO. So it is important to understand what keeps the DB team from delivering a solution that has better measured SLA. If they’re fighting similar problems as yourself such as legacy software and the business has made supporting that (even at the cost of torpedoing newer projects) higher priority you need to accurately and objectively show how your deficiencies are solely related to the organizational priorities. If the DB team is just run poorly, understaffed, etc. it’s even more important to be a politically aware engineer to be successful. Is there even any application or service that exists in your enterprise that can show high availability while using that database? Be careful to not become the pawn of a leader that is getting thrown under the bus by incumbents by being tasked with basically impossible duties and objectives. Even if the person’s intentions are noble that simply increases the chances of failure and your lessons therefore become lost (most large organizations and cultures seem to have a poor job reflecting carefully upon failures compared to trying to replicate successes no matter how circumstantial the nature of success).