This document discusses innovation through microservices. It begins by defining innovation as executing new ideas to create value for customers. It then discusses how to innovate through a microservices approach using a platform that allows for rapid deployment, lean analytics, and a build-measure-learn process to fail fast and learn quickly. This approach creates an antifragile system that gains from stress and shocks by measuring impacts and adapting in response.
3. • “Our primary aim is to transform the future from being a
liability in to an asset we can harness now”
• We don’t simply build products, we build tools and
prototypes to learn what products and features the
organisation should build
• If an initiative is not successful, we MUST learn
something of value from it
Tech Futures Innovation Team
10. Or
(Anything that teaches us what these experiences are)
VALUE ISTHE EXPERIENCESTHATTHE
CUSTOMER IS WILLINGTO PAY FOR
The Impact What we create
The Person we need to understand Whats in it for us
11. • Head off disruption
• create new wealth producing potential
• Learn to contribute to both above
Why Innovate?
15. • Companies in the bottom 10% of innovation investment
failed to benefit from structured innovation
• An upper limit of diminishing returns on investment
“It’s not about money. It’s about the people you have, how
you’re led, and how much you get it.”
- Steve Jobs
Money Isn’t Everything…
20. What is
POSSIBLE
with
Technology
What is
VIABLE in
Marketplace
What is
DESIRABLE
to Customers
Innovation
Business
Human ValuesTechnology
Design &
Interaction
Product
Manufacturing
Organisation
Behavior
Accounting
Finanace
Economic Anlysis
Policy
Marketing
Entrepeneureship
Competition & Strategy
Engineering
Analysis
Electronics & mechatronics
Programme Methodology
Operations
Information Technology
Chemical/Bio engineering
Software Delivery
Manufacturing Technology
Manufacturing Process
Supply Chain Management
Rapid Product Prototyping
Human Computer Interaction
Visual Thinking
Design sustainability
Aesthetic & Form
UX
WIreframes (prototypes)
Psycology
Anthropology
Socialogy
Ethnography
Need-Finding
Management & Teams
Human Resources
Organizational Dynamics
Negotiation
21. • Generate Ideas
• Select ideas
• Diffuse Ideas
Innovation Process in a Nutshell
23. Enterprise Innovation
Spin Off BAU
Skunkworks
Breakthrough
Sustaining
FitWithProcess
Fit With Values
Heavyweight
Team
Autonomous Org Mainstream Org
InHouse
Team
C A
D B
Poor Fit Strong Fit
PoorFitStrongFit
25. 1. Align innovation portfolio with customer needs and wants
2. Developing and retaining people with the right technical
knowledge
3. Ensuring that innovation leaders and business leaders are
aligned
4. Understanding new product and service related
technologies and trends
5. Pursuing lean product development
Innovation Success
26. • Reduce bureaucratic burden of implementing new
ideas?
• Empower EVERYONE to fail innovate?
• Explore rapidly changing technology landscape?
• Help the balance between governance and agility?
How can we reconcile?
27. • ground-breaking ideas don’t always look ground-
breaking when they launch
• Instead, they tend to build up out of a series of
experiments
• Focus on what you can afford to lose, rather than what
you might gain
• Don’t expect to have a great big idea come to you in
perfect form
Little Bets
28. • Take a micro-services approach to innovation
• Open to all
• Failure is very low cost
• Rapid development & re-use globally
• Ensure we learn from service interaction data
• Use learning to find winners for investment
Microservices
30. • Incubate & breed success
• Allow service to compete for supremacy
• Darwinian environment
• Life is cheap & microservices should be too
Innovation Platform
38. • When you solve a problems, you create a new one
• With deployment sorted now you’re worrying about new
stuff
• Data Consistency, Failure, Coupling, Insight, etc..
Convenience
39. • Fallacies of distributed Computing…
• Highly coupled HTTP calls
• Code proliferation to handle failure conditions
• Traditional transactional thinking becomes a problem
• No stack traces like code in a monolith for debugging
• Where are the unit & integration tests?
• How do you introspect to understand the whole?
Web Service Proliferation
41. Complicated
Service XYZ1 Service XYZ2 Service XYZ3 Service XYZ4
Service 3Service XYZ1 Service Z
Service 1 Service X Service 2 Service Y
Service 3Service Z Service Z
42. Complex
Service XYZ1 Service XYZ2 Service XYZ3 Service XYZ4
Service 3Service XYZ1 Service Z
Service 1 Service X Service 2 Service Y
Service 3Service Z Service Z
43. API Management
Service 1 Service 2 Service 3 Service 4
Admin UI
HTTP Proxy3HTTP Proxy1 HTTP Proxy2 Mgmt Svc
45. The Minilith
Service 1 Service X Service 2 Service Y Service 3
Service Z Service 4 REST API Service A Service B
EXPOSED REST API
Message Queue
46. Many Miniliths
Service 1Service A
1 2 3 4 5
6 6 API 8 9
API
Q
1 2 3 4 5
6 6 API 8 9
API
Q
1 2 3 4 5
6 6 API 8 9
API
Q
1 2 3 4 5
6 6 API 8 9
API
Q
1 2 3 4 5
6 6 API 8 9
API
Q
Message Queue
1 2 3 4 5
6 6 API 8 9
API
Q
REST API REST API
47. Higher Abstractions
Swamp of Pox
Resilience
Low Coupling
Insight
Data
Model
Analytics
EDA (Pipes)
Deployment Orchestration
Programming
Model
Eventual Consistency
Microservice Nirvana
54. • Every crash improves the system
• Safety systems exploit small errors
• redundancy duplicates critical components to increase
reliability of the system
Air Safety
55. • Species compete for domination
• Nature operatives with very little information yet excels at
survival
• Small iterative changes from generation to generation
• Don’t predict the future, be ready for multiple
eventualities
Nature
56. • Innovation is born out of necessity
• Anti-fragile systems are redundant, with countless
backup plans
• Not efficient, but effective
• Ready to take the lead if/when circumstances change
Innovation IS Antifragile
58. • Trail and error
• making do with what you’ve got
• recycle bits that would otherwise be wasted
• Rational trail and error is not random
• Recognise the favourable outcome and know what to
discard
Bricolage
59. • Failure
• Loss
• Chaos
• Learning
• Allow success to emerge
Embrace The Chaos
60. • Implement a lean platform
• With lean analytics In-built
• No need to ask for permission
• Create an Internal microservice app store for your
organisation
• Archive and reproduce services for future consideration
Incubate Success
61. • Platform mangement
• Define your architectural style
• Data model
• But don’t worry…
• What you can learn may be more valuable than technical
excellence
• Innovation embraces everything, including anti-patterns
Should I adopt micro services?
62. –Seneca
“It is not because things are difficult that we do
not dare, it is because we do not dare that things
are difficult.”