4 ms·
> A distributed system working against a single relational database, even if its just metadata, it's not only the ultimate anti-pattern but also sooo 2004 Perh
by mr90210 3y ago
> A distributed system working against a single relational database, even if its just metadata, it's not only the ultimate anti-pattern but also sooo 2004
Perhaps I wasn’t clear enough, but in your comment you make it sound that having multiple nodes interacting with a database is an anti-pattern, which is not, the discipline of distributed system is well researched and from the top of my head I risk to tell you that such anti-pattern is never mentioned, and the concept of a database rarely appears in DS, instead it focuses in a more abstract concept, which are the network nodes.
To support my argument, from the moment one decides to replicate nodes, most likely those same nodes will be connected to the same data source, because data replication isn’t as trivial as application replication.
In a Microservice architecture it can be considered an anti-pattern to have different bounded contexts using the same database.
- belter 3y agoNote I used the word relational databases. They must use connection pools because the database administrator, needs to protect the engine. Some DB engines even use a process per user connection, so it becomes very expensive on the server side. You need to multiplex thousands of connections, via a necessarily lower and upper bounded limited connection pool. The connection pool becomes the constraint. Use different, distributed, storage mechanisms, or basic Constraint Theory will come to bite you.