The Single Database per
Microservice pattern is a well established goal for Microservice
design and aligns with the Single Responsibility Principle,
though it is not as easily achieved as it seems when you
consider that there may be multiple instances of a given
Microservice, especially where those instances are spun up at
need by load balancing in the cloud under PaaS implementations.
As the author says in
an event-driven architecture a Microservice publishes an event
when it’s data changes and other services consume that event and
update their data. That is, of course, an oversimplification of
a process where duplicate notifications must be prevented. Also,
providing for eventual consistency in persistent datastores is
something that has to be addressed. This is where our effort to
figure out heuristics for scoping Microservices and their
interactive grouping can provide value. The question is how to
structure a set of interrelated Microservices such that they can
work together optimally.
Lots to think about.
Rex
On 2/2/2017 12:37 PM, Ken Laskey wrote:
This has been a continuing topic of discussion and I
found some info that actually covers this in the level of detail
where you an envision a solution.
How to maintain data consistency?
Thoughts? Continuing questions?
Ken
------------------------------------------------------------------------------
Dr. Kenneth
Laskey
MITRE
Corporation, M/S F510
phone: 703-983-7934
7515 Colshire
Drive fax: 703-983-1379
McLean VA
22102-7508
--
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670