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

Microservices

isa
February 21, 2014

 Microservices

Microservice architecture, governance, configuration, service discovery. Not much in the slides though, soon there will be a video link here..

isa

February 21, 2014
Tweet

More Decks by isa

Other Decks in Programming

Transcript

  1. Enterprise Applications ❖ What? (n-tiered; UI, Business, Persistence)! ❖ Types!

    ❖ Monolithic / COA! ❖ Service Based / Traditional SOA / ESBs! ❖ Microservices / HATEOAS
  2. Enterprisy Concerns ❖ Tons of them…! ❖ Development! ❖ Configuration!

    ❖ Integration! ❖ Transactional Guarantees! ❖ Maintenance! ❖ Deployment! ❖ Monitoring (logs, events, system, etc)! ❖ Performance / Load! ❖ Fungible Resources
  3. Traditional SOA ❖ Mostly vendor products! ❖ Not really a

    bus (more like service broker)! ❖ They are lying
  4. Traditional SOA ❖ Planned design! ❖ Change controls! ❖ Heavy

    configuration (u need dedicated folks)! ❖ Only EA group can tell you what to do! ❖ UDDI sh*t (sorry man, didn’t even work)! ❖ Hard deployments
  5. –Melvyn Conway “organizations which design systems ... are constrained to

    produce designs which are copies of the communication structures of these organizations..”
  6. Microservices ❖ Evolutionary architecture! ❖ Unix style (rock solid for

    more than 40 years)! ❖ Pipes of Business Values (single value each time)! ❖ Small footprint (less than 1K LoC)! ❖ Any technology (java, c#, ruby, python, etc)! ❖ No contracts (consumer driven contracts, tolerant reads)
  7. Typical Implementations ❖ Service Orchestrations! ❖ SPOF! ❖ There has

    to be an orchestrator! ❖ Choreographic alignment! ❖ Entities! ❖ Capabilities! ❖ Choreographies