On Tue, Apr 21, 2015 at 1:32 PM, firstname.lastname@example.org <email@example.com> wrote:
> "One kind of coupling that people tend to overlook as they transition to a
> microservices architecture is database coupling, where all services talk to the
> same database and updating a service means changing the schema. You need to
> split the database up and denormalize it."
> Am I the only one who feels somewhat nauseous reading that second sentence?
If your database isn't using the relational model anyway, then I'm not
sure that it's necessarily always true that normalisation is
beneficial. You have to weigh up the benefits of absolute consistency
of your data vs performance.
This message was posted to the following mailing lists: