The document discusses various technologies related to middleware messaging including JMS, Spring JMS, brokers like ActiveMQ, load balancing, queues vs topics, staged event-driven architecture, enterprise integration patterns, Camel, and monitoring with Spring Boot and Actuator. Key points covered include that JMS is a Java API for message-oriented middleware, Spring supports JMS, ActiveMQ supports multiple languages and is persistent/transactional, and Camel is an integration framework based on enterprise integration patterns.

1. Pablo Machado
machadoum@gmail.com
Mensageria

2. JMS
API da linguagem Java para middleware
orientado à mensagens. Através da API
JMS duas ou mais aplicações podem se
comunicar por mensagens.

3. JMS With Spring

4. JMS With Spring
https://github.com/bsnyder/spring-jms-examples

5. Brokers
http://predic8.com/activemq-hornetq-rabbitmq-apollo-qpid-comparison.htm

6. ActiveMQ
➔ Java, C, C++, C#, Ruby, Perl, Python, PHP
➔ Persistent, Transactional and Reliable
➔ Spring Support
➔ Designed for high performance clustering
➔ REST API

7. Load Balancing (workers)

8. Queue x Topic

9. Queue

10. Arquitetura SEDA
Stage A Fila A
Fila C
Fila B Stage C
Stage D
Stage B
Staged Event-Driven Architecture

11. Batch Provessing X Online Processing

12. Enterprise Integration

13. Enterprise
Integration Patterns
Lista de Padrões
http://www.enterpriseintegrationpatterns.com/toc.html
Talk
https://www.youtube.com/watch?v=Xwi1DU6KoQ4

14. Enterprise
Integration Patterns

15. Enterprise
Integration Patterns

16. Camel
Concise Application Messaging Exchange Language
“Apache Camel is a versatile open-source integration framework based on known Enterprise Integration Patterns.”

17. Camel

18. Camel

19. Monitor
JMX -> Jolokia -> REST -> Angular

20. Monitoramento

21. Monitoramento

22. Spring Boot
(+ Actuator)
http://start.spring.io/