Fichas
Microservices Talk
Fichas del conjunto (15)
- 1bounded contextread more about Book :
domain-driven design
2013
---all around talking the language of the domain-- a domain concept has a unique name,,, shipping domain has a bounded context call user, in the shopping domain you have a bounded context called user.
A context within which each context has its own unique environment - 2The more you know your businessbetter suited for microservices
what information makes sense in that "bounded context" - 3if one microservice calls 15 othersits built wrong
- 4Leave architectural decisions as far down the road as possible --Martin Fowlerffsd
- 5had problem of breaking monolith of client cable compnayused pact library---
parses json for testing pusposes. Sending json from back to front and front to back, to make sure changing one code base doesn't break other side. Each microservice can break the contract of expected json going back to front and - 6minilithsseparate bounded context as a file structure. Still a monolith, separated by "thin layer" to make microservices you thicken these walls and pull them out from each other
- 7who manages DB?App??
components?
DBAs??
depends on what framework, what istuation--- but ONLY touch one table per migration--- By touching one table per migration, it makes it safer to later split up components into microservice, if tables go multiple ways, easier to break when separating - 8moving closer to microserviceswithout overhead of multiple processes.
- 9Single biggest problem in breaking up code basescircular dependencies
- 10well structured monolithcan stop here, and be a lot better off than building microservices
- 11why microservices??every microservices extracted creates more issues.
---cause to scale up, bounded context has become an issue
--- to write software more frequently and deploy, Netflix deploys new software like every 15 min
Sam Newman -- Building Microservices - 12why not microservices?--cost of deployment is higher
Conways Law-- a communication pattern employed by a company will be reflected in their products.
--Dysfunctional communication pattern in the org
---creates a network inbetween your modules, networks not always reliable. it will fail at some point. Latency involved.
--extra module to route all the network calls around(FB uses 'eura')
--NEED extra extra app CIRTCUIT BREAKER DASHBOARD app to catch any error about to cause a "domino error" effect, and insert something that works after the first error. Now you have two extra services, just to handle microservicees architecture. - 13Talk Slides Code Exampleshttps://github.com/mikegehard/journeyFromMonolithToMicroservicesSlides
https://github.com/mikegehard/journeyFromMonolithToMicroservices - 14netflix runs around 150 microservicesphew!
- 15If you have boundaries wrong of your microserviceseasiest way is to smash it all up and build a monolith with all the services
Información
- Descripción
- MCAT Computer Studies Fichas sobre Microservices Talk, creado por ig ag el 12/09/2016.
- Creado por
- ig ag
- Visitas
- 6
- Valoración