1. A Microservices Journey
@christianposta

3. Christian Posta
Principal Middleware Specialist/Architect
Twitter: @christianposta
Blog: http://blog.christianposta.com
Email: christian@redhat.com
• Author “Microservices for Java developers”
• Committer on Apache Camel, Apache
ActiveMQ, Fabric8, others
• Worked with large Microservices, web-scale,
unicorn company
• Blogger, speaker about DevOps, integration,
and microservices

5. Microservices Journey
• Why?
• Microservices Architectures
• Cloud platforms with Kubernetes/OpenShift
• Q & A

6. If change is happening on the outside
faster than on the inside the end is in sight.
Jack Welch, former CEO, GE
S&P company life expectancy

7. Fortune 500 firms in 1955 vs. 2014;
88% are gone

8. We need to innovate, not just keep up.
(Red Queen’s Race)

9. Source: Dave Gray, The Connected Company

10. Source: Dave Gray, The Connected Company

11. Value delivered through services,
not mass production of product.

13. To deliver services which provide value,
we need to listen and react. We need
to deal with variety.

14. Software is eating the world.
Marc Andreesen

15. IT as a core competency; a driver
of business value

16. How to drive innovation and
deliver
value through IT:
• Decentralized decision making
• Purpose driven
• Innovation: Admit you don’t have all the answers;
figure out how to ask the right questions!

19. Characteristics of agile
systems
• Small teams
• Autonomy
• Own their existence
• Freedom + Responsibility
• Purpose driven
• Feedback/data driven
• Simple rules, emergent results

20. People try to copy Netflix, but they can only
copy what they see. They copy the
results, not the process.
Adrian Cockcroft, former Chief Cloud Architect, Netflix

21. “Let there be no more talk about DevOps
unicorns or horses but only thoroughbreds
and horses heading to the glue factory”
Dr. Branden Williams – business security specialist

22. Microservices Architectures

23. organizations which design systems ...
are constrained to produce designs which
are copies of the communication structures
of these organizations
Melvin Conway

24. “The microservice architectural style 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.”
Martin Fowler’s definition

25. “Microservices is an architectural approach,
that emphasizes the decomposition of
applications into single-purpose, loosely
coupled services managed by cross-functional
teams, for delivering and maintaining complex
software systems with the velocity and quality
required by today’s digital business”
Red Hat’s definition

26. Break things down (organizations,
teams, IT systems, etc) down into
smaller pieces for greater
parallelization and focus on reducing
time to value.

27. • Single, self-contained, autonomous
• Isolated and Resilient to faults
• Faster software delivery
• Own their own data
• Easier to understand individually
• Scalability
• Right technology for the problem
• Test individual services
• Individual deployments
What benefits of breaking this down?

28. Microservices is about optimizing… for speed.

29. Quick example

30. http://www.jboss.org/ticket-monster/

33. Microservices is about optimizing… for speed.

34. How do you go fast?

35. Shed dependencies!

36. How to shed dependencies?

37. Shedding dependencies
• Team self service
• Organize teams around a service
• Teams own entire lifecycle (build, test, deploy,
debug, operate, maintain; you build it you run it)
• Teams communicate via APIs (or you’re fired!)
• Services own their own data
• Boundaries establish a “bounded context”
• Services communicate via promises
• Make contracts explicit: contract evolution as a
first-class citizen

39. But we still have dependencies on
other services!

40. We need boundaries

42. Domain Complexity
• Break things into smaller,
understandable models
• Surround a model and its
“context” with a boundary
• Implement the model in code
or get a new model
• Explicitly map between
different contexts
• Model transactional
boundaries as aggregates

43. Services and teams make promises

44. Services make promises
• Health checking
• Autoscaling
• Self healing
• Circuit breakers
• Bulkheading
• Throttling/rate limiting
• Fallbacks
• Apologies

45. Services make promises

46. Consumer contracts?

47. Consumer contracts?

48. Consumer contracts?
{
"request" : {
"url" : "/user/ceposta",
"method" : ”GET”
},
"response" : {
"status" : 200,
"body" : ([
“first”: “christian”
“last”: 'posta'
“twitter”: '@christianposta'
]),
"headers" : {
"X-Application-Context" : "application:-1",
"Content-Type" : "text/plain"
}
}
}

50. • Have self-service infrastructure automation?
• Have self-service application automation?
• Have working CI/CD?
• Have health checking, monitoring,
instrumentation?
• Have logging, distributed tracing?
• Able to release services independently?
• Honoring backward and forward
Are you doing microservices?

51. • Maybe it doesn’t matter so much… What we
really care about is speed, reduced time to
value, and business outcomes.
• Maybe a data-driven approach is a better
way to answer this question...
Are you doing microservices?

52. • Number of features accepted
• % of features completed
• User satisfaction
• Feature Cycle time
• defects discovered after deployment
• customer lifetime value (future profit as a result of relationship with the
customer) https://en.wikipedia.org/wiki/Customer_lifetime_value
• revenue per feature
• mean time to recovery
• % improvement in SLA
• number of changes
• number of user complaints, recommendations, suggestions
• % favorable rating in surveys
• % of users using which features
• % reduction in error rates
• avg number of tx / user
• MANY MORE!
Are you doing microservices?

53. Are there any drawbacks?

54. • System complexity
• Operational complexity
• Testing is harder across services
• Security
• Hard to get boundaries right (transactions,
etc)
• Resource overhead
• Network overhead
Drawbacks to microservices

55. Microservices for Java Developers

57. • Simple configuration
• Curated dependencies and
transitive dependencies
• Built in metrics, monitoring
• Slim profile for deployment
(…micro even?)
#microprofile

58. Docker

59. • Distributed configuration
• Service Discovery
• Loadbalancing
• Circuit Breakers
• Bulkheading
• Versioning/Routing
• Based on AWS

60. What about non-java?

61. Kubernetes

62. Container cluster management
• Distributed configuration
• Service Discovery
• Loadbalancing
• Versioning/Routing
• Deployments
• Scaling/Autoscaling
• Liveness/Health checking
• Self healing

63. • Team self service application deployment
• Developer workflow
• Enterprise focused (LDAP, RBAC, Oauth, etc)
• Integrated Docker registry
• Jenkins Pipeline out of the box
• Build/deployment triggers
• Software Defined Networking (SDN)
• Docker native format/packaging
• CLI/IDE/Web based tooling
OpenShift is Kubernetes

64. • Elasticity, resiliency, self-healing, autoscaling
• Service discovery, load balancing, failover
• Logging, monitoring, tracing
• Configuration
• Testing
• Delivery
Declarative microservices

71. Twitter: @christianposta
Blog: http://blog.christianposta.com
Email: christian@redhat.com
Thanks!
BTW: Hand drawn diagrams made with Paper by FiftyThree.com 
http://fabric8.io
http://kubernetes.io
http://openshift.com
http://events.linuxfoundation.org/events/kubecon
https://github.com/pact-foundation
http://camel.apache.org