In order to find solutions for your problem (redefining the role of the database) you should look at how to analyze your software processes (data flow, dependen

In order to find solutions for your problem (redefining the role of the database) you should look at how to analyze your software processes (data flow, dependencies, coupling). Being a good architect, in my opinion, is all about analyzing "what's there" and finding ways to transform that into "what should be there which is better because X". What helps me most when analyzing an existing system/architecture is visualizing it. When I can see the thing with my eyes, there are usually all sorts of visual cues that lead to the actual problem(s) with a specific architecture and that is often a good starting point for making changes. Sorry, if my advice may seem a bit generic or simplified.