2 ms·
> But why the hell are you putting two databases into the architecture out of the gate?! > There are a couple of reasons for this. Primarily I feel like the ac
by bob1029 3y ago
> But why the hell are you putting two databases into the architecture out of the gate?!
> There are a couple of reasons for this. Primarily I feel like the access patterns for the customer are sufficiently different to business access patterns and have different requirements.
The central problem I see with every article like this is the author's "business" and my business are entirely different universes. "Different requirements" is the entire game. Everything depends on the customer's expectations. When I read stuff like this I sometimes wonder if we are even speaking the same language.
For me the "Red Tortoise" architecture is to start with A SQL database and iterate the schema with business owners and customers until everyone is so bored with how obvious it all is that they have to take frequent breaks for naps.
I could take articles like this more seriously if there was some kind of introductory section that explained the actual business/problem that needed solving. Otherwise, this feels like a pointless shiny technology rabbit chase through the fields of "what if?".
- brudgers 3y agoI agree that context is missing. But I can't think of an obvious class of business problems where the database schema for a customer facing system wouldn't be served by working hand in hand with the customer. But, that is probably due to my cognitive limitations, lack of specific experience, or absence of knowledge regarding the context you are thinking of. Can you give some context to the sort of problems you are focused on? Thanks.
- m0llusk 3y agoGovernment regulation compliance: It is necessary to make accounts, verify identity, request and pay for licenses. Following rules, displaying required notifications, enforcing compliance with fines or status changes all comes across to most members of the public as completely byzantine and incomprehensible. All of that needs to start with government officers who understand the related legal landscape.
- gmfawcett 3y agoIt depends. In some applications, the business users are SQL power users who live and work in the schema, and every bad design choice hurts them every day. But in others, the schema is fully hidden behind UIs and canned output (reports, dashboards, ETLs). It never sees sunlight, so many bodies can be buried. Even custom, tailored software often gets deployed as SaaS these days.