nitter
Stefan Tilkov
@stilkov
3 Dec 2016
I don't think they are, but I think they should be
Eberhard Wolff
@ewolff
2 Dec 2016
Maybe separated databases are the core of Microservices like architectures.
Dec 3, 2016 · 10:03 AM UTC
4
2
6
Eberhard Wolff
@ewolff
3 Dec 2016
Replying to
@stilkov
.
@stilkov
you want to decouple two components. What's more important: separate deployment or separate database schemas?
1
Stefan Tilkov
@stilkov
3 Dec 2016
Inseparable: If database schemas are shared, development and deployment need to be synchronized every time there's a schema change
4
1
1
more replies
graste v4.4
@mivesto
3 Dec 2016
Replying to
@stilkov
Maybe coupling is seen as easier to handle as creating proper distributed systems w/ eventually consistent data & unversioned APIs
1
Stefan Tilkov
@stilkov
3 Dec 2016
Completely undisputed – far easier up to a certain size (though I do wonder why people split them up in the first place, then)
1
more replies
Eberhard Wolff
@ewolff
4 Dec 2016
We are not advocating shared schemas. We are just wondering how important separated schemas are.
Mark Struberg #jesuisheisl
@struberg
3 Dec 2016
Replying to
@stilkov
separating databases has a few pros but many cons as well! It also depends how 'big' a
#microservice
is. Most cut way too tiny!
Mario Mueller
@xenji
3 Dec 2016
Replying to
@stilkov
@ewolff
we are doing db sep. currently as the first step