Navigating Identity and Access Management in the Modern Enterprise
Microservices Minus the Hype
1. Microservices Minus the Hype
Mark Heckler
Principal Technologist/Developer Advocate
mark@thehecklers.org
mheckler@pivotal.io
@mkheck
2. Who am I?
• Author
• Speaker
• Architect & Developer
• Java Champion
• Survivor of many monoliths
• Seeker of a better way
3. Fighting the next war, not the last one
We make decisions based upon the best data available at that point in
time...but the world doesn't just stop
The best possible decisions at any given point in time aren't evergreen
As the technological landscape shifts, better decisions come into view
Trust that best decisions were made
Learn from the past, apply to the present to build the future
11. –Martin Fowler, “Microservices and SOA”
“…the microservice style is very similar to what some advocates of
SOA have been in favor of. The problem, however, is that SOA means
too many different things, and that most of the time that we come
across something called ‘SOA’ it’s significantly different to the style
we’re describing here, usually due to a focus on ESBs used to integrate
monolithic applications.”
12. “The Great Debate: Microservices vs SOA”
“Microservices is an evolution of SOA concepts that can provide
additional benefits to adopting organizations. The benefit of
Microservices over ‘traditional’ SOA is speed and agility for making
changes, and the ability to make changes with less overall cost and
less impact on the existing infrastructure. Microservices involves a
different approach, as well as some different uses of technology.”
15. All about that (Enterprise Service) Bus
Monitor and control routing of message exchange between services
Resolve contention between communicating service components
Control deployment and versioning of services
Marshal use of redundant services
Cater to commodity services like event handling, data transformation and mapping,
message and event queuing and sequencing, security or exception handling,
protocol conversion and enforcing proper quality of communication service
25. The Play-DohTM Principle
It's always easier to combine small, self-contained code or data than it is
to decouple code or to parse data.
26. How to start
Can’t just unplug the monolith(s) & go greenfield
Build interfaces
Choose volatile functionality
Leverage patterns, components, & tooling
31. –Marc Andreessen
“In my view, because the companies that do
can then innovate much more quickly than the
companies that don’t.”
Why are microservices and cloud-native technology important for every
business to adopt (and not just startups)?