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

Data Dichotomy

Data Dichotomy

Problema dos dados na arquitetura de micro serviços

Andre Fonseca

January 27, 2017
Tweet

More Decks by Andre Fonseca

Other Decks in Technology

Transcript

  1. DATA DICHOTOMY Data system are about exposing data. Services are

    about hiding it http://vignette2.wikia.nocookie.net/memoryalpha/images/e/e7/Data_makeup_tests.jpg/revision/latest?cb=20120725111417&path-prefix=en
  2. https://martinfowler.com/articles/microservices.html “ … In short, the microservice architectural style [1]

    is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies… "
  3. • Polyglot (best tool for the job) • Scaling •

    Distributed • Reduced number of LoC / PROS
  4. • Database aren’t easy to scale (shards, shared files, etc)

    • Single point of failure. • Not polyglot • Hard evolving: if you change some scheme, you need to adapt all services that use it. • Not isolated