Integration architecture for a global beverage company
A global beverage company planning a digital transformation needed a new data exchange and integration strategy between regional on-premise and cloud systems, on MuleSoft Anypoint Platform and CloudHub. We ran the workshops, built the canonical data model and designed a hybrid architecture that reused the existing endpoints instead of rewriting systems that were already in maintenance.
- Global
- regional on-premise systems and cloud applications on one exchange layerEngagement
- 0
- existing endpoints re-implemented: REST, SOAP, FTP and IBM WebSphere MQ reused as they wereArchitecture
- Sized
- to the client's actual and projected data volumes, with MuleSoft architectsScaling exercise
- Client
- A global beverage company
- Sector
- Consumer goods; enterprise integration
- Engagement
- Architecture consulting: on-site workshop, data exchange matrix, canonical data model, scaling and platform proposal
- Stack
- MuleSoft Anypoint Platform, Mule Runtime and CloudHub; REST, SOAP, FTP and IBM WebSphere MQ endpoints
- Offer today
- Technical Due Diligence and Microservices consulting
A system portfolio in maintenance, and a transformation that could not afford to touch it
The company was designing a new data exchange and integration strategy between regional on-premise systems and cloud applications, had selected MuleSoft with Anypoint Platform and CloudHub, and was looking for an experienced consultancy to support planning and integration design. Most of the existing systems were in their maintenance stage; amending each of them to fit a new integration layer was not an option.
Workshop, data exchange matrix, canonical model, sizing
Our MuleSoft consultant worked alongside MuleSoft account managers and a partner company to keep the design within integration best practice and tailor the platform to the client's needs. The project started with an on-site workshop to identify the key systems, their stakeholders, technical maturity and integration readiness.
The central artefact was a data exchange matrix: a top-level conceptual data flow graph, extended with system-specific data entity definitions, from which we built a canonical data model for the exchange layer with detailed entity and attribute mappings and the transformations required. The technical analysis also established current and projected data volumes and the available security controls, and a final scaling exercise with MuleSoft architects sized the platform.
What the architecture gave the client
- Reuse
- a hybrid architecture connecting older systems and cloud applications over the protocols they already spokeDesign
- No rewrites
- a modern, high-performance design without amending individual systems in maintenanceDesign
- Right-sized
- a Mule Runtime and CloudHub proposal scaled to the client's volumes and hardware optionsProposal
The offers this engagement proves
Book a scoping call
Thirty minutes with an architect, not a salesperson. You leave with a written view of scope, price model and whether we are the right team for it.