6. Business is shortsighted
Business wants to deliver the best experience
to the customer with the lowest investment
and as fast as possible
Teams often compete for budget and not
often most future proof idea get
implemented
8. The agile enterprise
Enterprises thrive to be more adaptive
They understand that the market need
changes by the day
Organizations have to enable organic
growth via new channels
New challengers, but new opportunities
9. Reality of enterprise systems landscape
Enterprise systems are complex
Enterprise systems are bureaucratic
Cannot afford the luxury of complete re-write or
having a clean slate
Comes with years of baggage
10. Mainframes
… with monoliths
Distributed systems
… with monoliths
… then SOA
Cloud servers
… with monoliths
… then SOA
… then micro-services
Waterfall Scrum XP (Agile*)
The sliding window effect of EA
11. Micro-services finally deliver on the promises of SOA
Explicit boundaries
Shared contract and schema, not class
Policy-driven
Autonomous
Wire formats, not Programming
Language APIs
Document-oriented
Loosely coupled
Standards-compliant
Vendor independent
Metadata-driven
Modelled Around Business Domain
Culture Of Automation
Hide Implementation Details
Decentralize All The Things
Deploy Independently
Consumer First
Isolate Failure
Highly Observable
14. REST/JSON/Swagger is the new normal
Messaging style/format is widely standardized to
REST/JSON
API documentation for discovery is standardized
around swagger
Wider language and framework support (MSF4J,
Spark, Springboot etc.)
16. API comes at every layer
Frontend JS
UX API
Business
API
Application
API
Data API Infra API
Device
optimized
Business
rules
Business
content
Products &
services
CRM
ERP
HR
Master
Marketting
History
Relations
Devices
Virtual
Automation
OpsIntegrationWorkflow
17. The right solutions architecture
Is iterative – continuous improvement
Goal driven
Caters to the business
Thinks beyond MVP – extensible
Futuristic technology selection
Right vendor selection
Flexible & resilient
Can accommodate change
Right assumptions
Right tradeoffs
18. QoS drives the deployment
High availability
Redundancy
Data replication
Caching
Internal vs external
Geo distribution / location
sensitive
Deployment automation
Systems update
Recovery latency
19.
20. Hand holding starts
Marketing the API platform
Tutorials, samples, case studies and talks
Sponsored hackathons
Partnerships
21. TfL’s Data in Motion Hackathon
https://blog.tfl.gov.uk/2016/10/04/data-in-motion-hack-week-event-review/
24. References
Choosing an API and SOA Governance Architecture (Gartner research) - https://goo.gl/MTsE4g
Building a Digital Business Technology Platform (Gartner research) - https://goo.gl/vzN34e
API Management: The missing link for SOA success - https://goo.gl/HKDHs0
Building Microservices: Using an API Gateway - https://goo.gl/jBVk6m
Microservices in Practice - Key Architectural Concepts of an MSA - https://goo.gl/cbQMnl
Docker, and Why Containers Matter - http://www.slideshare.net/relistan/docker-and-why-
containers-matter
2016 State of Digital Transformation - http://www.huffingtonpost.com/vala-afshar/the-2016-
state-of-digital_b_12074114.html
Consumers are needy, they are connected and has social media circls
This about how consumers drive how content and services delivery aspect.
A business now cannot stick to one media
Amazon for example – alexa / dash etc
This about how consumers drive how content and services delivery aspect.
A business now cannot stick to one media
Amazon for example – alexa / dash etc
This about how consumers drive how content and services delivery aspect.
A business now cannot stick to one media
Amazon for example – alexa / dash etc
Business wants to deliver the best experience with lowest investment in the shortest time possible
- Comitition for budget
It’ll occur to every one sooner or later
Enterprise ecosystems are complex, the challenge is to become agile to cater to the fast evolving echo system
New mediums popping up everyday (IOT stuff)
Everybody is a app developer, modern organization have to be an enabler
New challenges, but new opportunities
Complexity is added for necessity
- Many different laws (HIPA, banking laws, federal etc)
Have to serve a spectrum of clients cannot afford a complete reset easily
100 years of history
EA is constantly evolving, new paradigms emerge to support complex requirements
Standards and patterns emerge to simplify the existing (Micro-services, SOA done right)
EA adapts to the business (Focus on the core business / run ur servers elsewhere)
EA has to become agile and iterative
Finally the technology landscape is ready for proper SOA and that’s called micro-services
ESB is pushed a layer down
NoESB architecture has to be properly understood
SOA is becoming more API oriented
SOAP is getting transformed more and more
EA has recognized the right place of the API gateway and its purpose
It’s a mix of things the ESB did and the micro services architecture didn’t do
Service governance
Discoverability
Throttling
Security
Monitoring
In summary policy enforcement
SOAP/XML has become legacy baggage
Often SOAP/XML is converted to REST/JSON
WS-Security is dead
OAuth / OIDC / JWTs solves security
If ur starting from scratch, this is the key
A type of an application is just of of the many faces
APIs facilitate this incomprehensible scale
APIs create the MVP
If ur starting from scratch, this is the key
A type of an application is just of of the many faces
APIs facilitate this incomprehensible scale
MVP at every stage
Is the flexible one
Start small for your immediate to 6 – 12 months expectations
Make sure the decisions you take and technologies you choose are flexible
Iterative SA
Unless ur Amazon or Google you don’t want to maintain a highly available m-dc deployments
But you still needs more than four 9s out of ur solution
You still need Internal traffic to route internally
And your European customers served with less than 200ms latency (trans pacific latency is ~100ms)
- Did we make enough traction
Are people using and publishing APIs
Is ur partners using APIs
Creating a platform
Creating a API echo system within and outside (TFL example)
Creating a platform
Creating a API echo system within and outside (TFL example)
One solution for every problem ?
Can we solve everything with MSA ? APIs ?
ESB is bad
The is no right or wrong. Its all tradeoffs