Microservices, with JBoss EAP & OpenShift

1. Microservices
with
JBoss EAP & OpenShift
(and more)
Bob McWhirter

2. Who is Bob?
• Bob McWhirter
• Project lead for WildFly Swarm
• Founder of…
• Drools
• The Codehaus
• TorqueBox
• Director of Research & Prototyping, JBoss

3. Microservices

5. • Helps define architecture
• Independent release cycles
• Accelerate business velocity

6. All of this requires
discipline

8. • Each service does one thing
well,with well-defined bounds
• If it used to be a library, it’s
probably a service now

9. ServiceWell-defined
Inputs
Well-defined
Outputs

11. • Loosely coupled implementations
• Loosely coupled locations

12. Which leads us to …

14. “organizations which design
systems ... are constrained to
produce designs which are copies
of the communication structures of
these organizations"
–Melvin Conway

15. A
monolithic organization
produces
monolithic software

16. Which leads us to …

18. A meeting should never have so many
attendees that they could not all be fed
with two pizzas.
Generally, this limits the number of
attendees at a meeting to less than
eight.

19. Therefore, your bounded-context
should be something solvable by
less than 8 people…
including the Product Manager.

21. From the MicroProfile example
• Sessions
• Speakers
• Schedules
• Attendees

24. Caveats…

25. If you failed at SOA,
you’re probably going to fail at
microservices.

26. Monthly/Weekly/Hourly
releases
of 200 microservices
is not easy

27. Things that can help

29. Because what’s tested is
exactly what should be
deployed

31. If you’re deploying
continuously, you should be
building continuously

33. If you’re deploying
continuously, automated
provisioning is useful

34. And things like OpenShift can
provide cross-cutting
functionality

35. So you want to write a
microservice…

37. My App
JBoss EAP

39. 95% of
My App
JBoss EAP
Service
#1
JBoss EAP
Network

41. 90% of
My App
JBoss EAP
Service
#1
JBoss EAP
Network
Service
#2
JBoss EAP
Network

43. Service
#2
Service
#5
Service
#4
Service
#1
Service
#3

50. If I have 45 small
services, why EAP?

52. • Wraps the server around your service.
• Built upon WildFly/EAP.
• Smaller footprint.
• Single deployable artifact.

53. JAX-RS
CDI
JMS
JPA
Batch
Bean Validation
JCA
JMX
Naming
…more!

54. Jolokia
NetflixOSS
Logstash
Keycloak/Red Hat SSO
Swagger

55. Service
#2
Service
#5
Service
#4
Service
#1
Service
#3

56. Thanks!