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

[Portuguese] Moving from a Monolithic to a Microservices Architecture

[Portuguese] Moving from a Monolithic to a Microservices Architecture

In 2006, service oriented architecture (or SOA) was all the crazy, but it failed us. Microservices resemble a lot with SOA, but if SOA didn’t work in the past, why are we back again with the same principles? Are Microservices just SOA in disguise?

This talk was created to demystify it, showing what was inherited from SOA and what is different now that allows us to resume the journey we abandoned 10 years ago. It will focus on things with which I struggle, in my own experience of moving from the monolith to an army of well-defined microservices.

Let's go through some of the most important patterns and see how to avoid the most common pitfalls.

Artur Caliendo Prado

May 29, 2017
Tweet

More Decks by Artur Caliendo Prado

Other Decks in Programming

Transcript

  1. View Slide

  2. View Slide

  3. View Slide

  4. Monolith

    View Slide

  5. De
    Monolito para
    Microsserviços

    View Slide

  6. Artur Caliendo Prado
    [email protected]
    @artur.prado @artur_caliendo
    @arturcp

    View Slide

  7. Não siga o
    mantra

    View Slide

  8. View Slide

  9. Monolith Microservices

    View Slide

  10. View Slide

  11. Why not a monolith?
    Ferramentas
    Linguagem
    Processos
    Tempo de deploy
    Bibliotecas

    View Slide

  12. Microservices

    View Slide

  13. Share “nothing”

    View Slide

  14. View Slide

  15. View Slide

  16. View Slide

  17. Availability vs Responsiveness

    View Slide

  18. View Slide

  19. View Slide

  20. View Slide

  21. View Slide

  22. View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. View Slide

  27. View Slide

  28. View Slide

  29. View Slide

  30. View Slide

  31. View Slide

  32. View Slide

  33. View Slide

  34. View Slide

  35. http://www.oreilly.com/programming/free/

    View Slide

  36. View Slide

  37. [email protected]
    @artur.prado

    View Slide