[cbono1]

Thanks for the reply!

For the folks you worked with in the past that were excellent, were they full time DBAs in terms of their title? Or were they folks that were in other departments (i.e. devops) that also had expertise in good DB design in scaling?

It might also depend on the size of the company the particular need? Evolving a monolith-like DB already in production to a better structured state might be much to ask of an individual.

[DevKoala]

I just checked the LinkedIn of the individual whom I consider excellent, and his title is actually Database Architect. I feel that is fair considering his skills and the projects I know he handled.

Everybody in that engineering org worked with big data and could design the data store system for a regular startup easily. However, this individual’s role was to optimize our multi tenant PG cluster design to build some complex CDP functionality on top of it.

I now work for a larger organization and when I run into the individuals that own shared database resources all they do is impose contrived read/write permissions. However it makes some sense since I work with PII in some cases.

[cbono1]

Got it, yea seems this is more valuable in a big data context or when actively pressed up against scale limitations of a DB deployment. Funny on the the last piece as well - appreciate the thoughts here!