O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Microservices for AEM by Maciej Majchrzak

1.426 visualizações

Publicada em

Microservices for AEM by Maciej Majchrzak

Publicada em: Tecnologia
  • Seja o primeiro a comentar

Microservices for AEM by Maciej Majchrzak

  1. 1. Microservices Architecture for AEM Maciej Majchrzak / majchrzak_m
  2. 2. System architecture
  3. 3. What?
  4. 4. What? With what?
  5. 5. What? With what? How?
  6. 6. What? With what? How? What next?
  7. 7. http://woms.dyndns.org/fashion-designer-clothing.html
  8. 8. Scalability
  9. 9. Simple AEM system
  10. 10. Scalability (1) Caching layer
  11. 11. Scalability (1) Caching layer
  12. 12. Scalability (2) AEM layer
  13. 13. Simple AEM system Complex system
  14. 14. Scalability
  15. 15. • Development • Deployment • Scalability • Time to market and cost Challenges
  16. 16. Microservices architecture
  17. 17. Architecture
  18. 18. {{ /search/adverts }}
  19. 19. Architecture Scalability
  20. 20. Architecture Scalability Performance
  21. 21. Traditional approach
  22. 22. Microservices approach
  23. 23. TraditionalMSA
  24. 24. Architecture Scalability Performance Development
  25. 25. https://flic.kr/p/4gLRqc Benefits
  26. 26. • Improved scalability – you can scale a part of the system which really needs it. You don’t need additional AEM licences to scale heavy-processing part of the system, like search, user management, etc. • Faster development – you can use technology which best suits your needs, you’re no longer limited to AEM/OSGi stack. You can also separate your teams easily as they may work on separate applications with seperate technology stacks. • Better performance – the system is performing better and more stable than a pure AEM-based one • Increased agility – thanks to well seperated services any change introduction is simpler and takes less time Benefits
  27. 27. Benefits Drawbacks
  28. 28. • More complicated infrastructure • More discipline needed during design and services maintenance Drawbacks
  29. 29. Benefits Drawbacks Success factors
  30. 30. • Infrastructure provisioning and deployment automation – tools like Chef and Vagrant are your friends • Be careful when deciding what should be a separate service Success factors
  31. 31. Benefits Drawbacks Success factors Take- aways
  32. 32. Q&A majchrzak_m

×