Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Not a SO(A) Trivial Question!

Not a SO(A) Trivial Question!

MuCon presentation about the legacy of SOA and its influence on Microservices today.

Tareq Abedrabbo

November 07, 2017
Tweet

More Decks by Tareq Abedrabbo

Other Decks in Technology

Transcript

  1. Background • Some organisations are starting greenfield microservices projects •

    A few are trying to evolve preexisting platforms • Many of these organisations have a SOA heritage
  2. “A service has four properties according to one of many

    definitions of SOA: 1.It logically represents a business activity with a specified outcome. 2. It is self-contained. 3. It is a black box for its consumers. 4. It may consist of other underlying services.”
  3. ➡ An architectural style and design patterns ➡ Data models

    and patterns ➡ Technology and tools (ESBs, GUIs) ➡ A collection of specifications (SOAP, WS-*)
  4. • Using ESBs (or similar) • Ignoring delivery guarantees/expecting transactions

    • Excessive marshalling/unmarshalling • Canonical data models/complex schema • Distributed monolith (based on lack of understanding of boundaries) • Minilith (proliferation of technology, databases) • lack of automation in infrastructure/testing
  5. Recommendation • No canonical data model (services do not need

    to understand every aspect of the service) • canonical data model vs schemas • Separate data from meta-data • Data orientated modelling/schemas • Normalise meta-data