2020-05-04 Monday - A Metaphor for The Absence of Enterprise Architecture

Public Domain

A beautiful inverse metaphor for the practical value of Enterprise Architecture and Governance.

Put another way, a perfect example of the __absence__ of Enterprise Architecture.

Today's analogy: Every user/department - deciding to have their own dedicated/different application. No reuse. No governance. Also, point-to-point integration strategies, tight coupling, and single points of failure.

A telephone tower in Stockholm, Sweden, 1890. The tower served 5,500 subscribers. Each subscriber had their own dedicated cable.

• https://rarehistoricalphotos.com/the-stockholm-telephone-tower-1890/

2019-08-07 Wednesday - Microservices Saga Pattern

Photo by Eduardo Flores on Unsplash
https://unsplash.com/photos/qJ4FCI0sx98

In Madhuka Udantha's recent DZone article, Design Patterns for Microservices,  I noted he placed the Saga Pattern in a Database Pattern collection.

I wonder if this is perhaps because he is defining it in a strict alignment with the original 1987 paper by Hector Garcaa-Molrna Kenneth Salem?

It seems misplaced though there, to me...given the utility of Saga Pattern for orchestration, choreography, or database coordination...

Typically, I think of the Saga Pattern in terms of a type of Integration Pattern...of which orchestration or choreography could be just subtypes...if not outright peer level collections to the Database level collection that he defines...

Since the Saga Pattern may be used to manage the loose orchestration with other services (either internal, or external) - but may not be dealing directly with a database at all - the placement in Database collection seems out of place...?


Background Reading:

See Arnon Rotem-Gal-Oz's 2012-2013 blog postings:

• https://arnon.me/soa-patterns/saga/
• https://arnon.me/2013/01/saga-pattern-architecture-design/

Chris Richardson's article, from earlier this year - which aligns more closely with  Madhuka's name grouping...

• https://microservices.io/patterns/data/saga.html

Distributed Sagas for Microservices, by  Yos Riady (2018)

• https://dzone.com/articles/distributed-sagas-for-microservices

Saga: How to implement complex business transactions without two phase commit, by Bernd Rücker (2018)

• https://blog.bernd-ruecker.com/saga-how-to-implement-complex-business-transactions-without-two-phase-commit-e00aa41a1b1b

You may also find these patterns in Thomas Erl's site (re: Arcitura Education Inc) of interest:

• https://patterns.arcitura.com/microservice-patterns/design_patterns/micro_scatter_author
• https://patterns.arcitura.com/microservice-patterns/design_patterns/microservice_compositor