This is the presentation I gave at WSO2con 2013 in which I shared with the experience implementing SOA at the Ministry of Infrastructure and the Environment in the Netherlands. The challenges the ministry faced as an organisation that has outsourced it’s IT. How these challenges affected the SOA strategy and how some of these challenges were addressed with WSO2 products.
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
The challenges of successfully executing a SOA strategy in a complex outsourced environment
1. How WSO2 helped save Euro 500K and
Presentation title
deliver SOA solutions faster
By Stephen Oostenbrink
The Ministry of Infrastructure and the Environment
2. The Ministry of Infrastructure
and the Environment
How WSO2 helped
save Euro 500K and
deliver SOA solutions faster
Stephen Oostenbrink
Enterprise Architect and Technology Evangelist
9. Enterprise architecture is part
of the governance organization
Service Information Enterprise Application
Management Management Architecture Management
11. Complex environment
(simplified view ) civilian
Internet
BASE
registries
Rijksconnect KPN company
Prolocation
BASE
registries
authorities
Diginetwerk
SSC ICT
authorities
Atos
BASE Rijksconnect
registries
Diginetwerk
DICTU company
12. The SOA promise
System
ws ws ws
Monolithic System
Building Base
Registries
Blocks Registries
13. The SOA headache
1st rule of integration: It will fail, you don’t know when!
2nd rule of integration: It will FAIL, you don’t know when!
3rd rule of integration: When it fails parties will be pointing at each other.
The rules of Fight Club
23. 7. Missing a reliable platform
to build on civilian
ebMS adapter
ESB (Product F) Internet
(Product A)
ESB
BASE
registries
Rijksconnect KPN (Product B) company
Prolocation
BASE
ebMS adapter registries
(Product E)
ESB Diginetwerk authorities
(Product D) ebMS adapter
(Product G)
ESB
SSC ICT (Product C)
authorities
Atos
BASE Rijksconnect
registries
Diginetwerk
DICTU company
27. Focus on the foundation
Evangelise SOA vision and Get involved
strategy
Build skills and expertise Implement basic platform
28. Selected an ESB focussing
on 4 key criteria
Dutch government Manageability
interoperability standard
Open source Modular setup
29. Comply with the Dutch government
interoperability standard
WUS (WSDL, UDDI and ebMS (ebXML Messaging
SOAP) + WS-RM Service)
PKI certificates Large message standard
34. The foundation required
additional functionality
Insight in service usage
Business Activity Monitor
Fully automated
Governance Registry
deployment
35. Centralizing connectivity and moving control to
the application level civilian
ebMS adapter
Enterprise Service Bus
Internet
Enterprise Service Bus
ESB Identity Server
Rijksconnect KPN Business Activity Monitor company
ProlocationRegistry
Governance
BASE
registries
Enterprise Service Bus
ESB authorities
Diginetwerk
SSC ICT ESB
Enterprise Service Bus
authorities
Atos
ESB
Enterprise Service Bus
Rijksconnect
Diginetwerk
DICTU company
36. Next steps: roadmap
Shift from web service to
API model API Manager
Enhanced manageability
from application level
Improve and expand the
platform
37. This shift will result in
regaining control
Now Near future
Business value In control
€€€€ Application Application €€€
Middleware Middleware
€€
Infrastructure Infrastructure
Commodity Dependency
38. Products
Accessibility
Support
Documentation
Code comments
WSO2: the good, the bad and the ugly
(what we like) (room for improvement) Community
involvement
39. Summary
New paradigm In the trenches
People and technology Chain management
Evangelise Right platform
Expertise and experience Right partners
41. No, saving more than € 1
million in 3 years
ESB products phased out € 950K
Reduced development, deployment and operational costs € 250-500K
Reduced infrastructure and middleware costs € 200-300K
Estimated savings next 3 years € 1.400-1.750K