I don't think they are, but I think they should be
Maybe separated databases are the core of Microservices like architectures.
4
2
6
. @stilkov you want to decouple two components. What's more important: separate deployment or separate database schemas?
1
Inseparable: If database schemas are shared, development and deployment need to be synchronized every time there's a schema change
4
1
1
so the separate schemas are in a way more important
2
1
no they're not. You can treat tables as public and not make incompatible changes to still benefit from separate deployables
2
1
Replying to @jkuipers @ewolff
Similar to how you can just build a modular monolith: True, but a technical boundary helps

Dec 3, 2016 · 12:01 PM UTC

1
Replying to @stilkov @ewolff
most devs treat their APIs the same as a backwards comp. DB table: no versioning (1 version only), bad docs, no guarantees
1