2 ms·
Dealing with fairly low-volume stuff, my concern about using the database alone has to do with who owns what schema and how changes are managed. Being able to
by Terr_ 9y ago
Dealing with fairly low-volume stuff, my concern about using the database alone has to do with who owns what schema and how changes are managed.
Being able to send off a rich asynchronous message is nice because it means you do not need to have some co-owned table in a shared database that two different components are reading and writing from.
Or, worse, a widespread pattern of every service exposing a piece of its database to other services with an unsatisfying level of logging or control for what really happens.
- woodrowbarlow 9y agonot all databases require rigid schemas. a filesystem, for instance.
- Terr_ 9y agoI don't understand what distinction you're trying to raise. My point is that a message-queue allows you decouple systems, whereas having two systems share the same database tables has its own kind of peril.