Because a Microservices Architecture fundamentally changes how organizations think about databases and the data layer, many know they want to adopt it but struggle with making it happen. Going from centralization to distribution requires shifts in mindset as well as in organizational/team structure. Plus, DDD requires a deep knowledge of your domains. Perhaps your organization suffers from poorly defined (or unclear) business domains. Either way, getting service-boundaries wrong can be expensive. These are all common challenges to adopting a Microservices Architecture. We’ll help you overcome them.Our Kickstart helps your organization plan its migration to Microservices by pursuing an incremental approach to adoption. Additionally, we perform a dependency analysis, using logical modeling to identify domains and visually assess domain coupling. Further, we help your organization embrace Domain-Driven Design: the design standard of Microservices. Based on Bounded Contexts, DDD organizes and models software design around core business domains (vs. technology elements).
The Microservices Architecture Kickstart follows three key steps, typically over a three-week period:
We begin by setting business-impact objectives to measure and track the benefits of Microservices. These include Business and IT alignment with major initiatives and priorities, and establishing key qualitative/quantitative drivers. Next, we identify any existing gaps related to legacy systems and architecture. Lastly, we establish a baseline by performing a current-state analysis that includes your people (structure, skill sets, COE’s), process (architecture patterns, standards, governance) and technology (monolithic systems, tech stack, supporting infrastructure).
This step identifies your solution layers and components and API Management/API Gateway components. Additionally, we consider your security components, service-design principles and patterns, and development technologies and toolset options. We determine your environmental and integration needs and readiness along with assessing your IT control and manageability, and exploring options for ongoing monitoring and solution analytics. We also conduct facilitated ideation sessions to discuss any monolithic legacy systems and construct a scenario matrix for the decomposition of their business domains. High-level domain-modeling exercises help drive our prioritization analysis and facilitate the mapping of core domains to current systems. Lastly, we score and rank domains based on key criteria (e.g., business driver impact, ease of decomposition, organizational readiness) in preparation for building your Roadmap.
Our Phased Implementation Roadmap is based on the alignment of systems and domains with your drivers and objectives, dependencies, and cost/effort considerations. The immediate (phase I) action plan includes the scope of systems/domains and services, and the approaches for design and development, migration, and budgeting. Finally, we provide specific next-step recommendations to achieve our envisioned “to-be” Microservices Architecture, based on existing gaps, overall readiness, and critical dependencies.
Summarizes key business drivers, priorities and Microservices initiatives.
These guiding principles to govern your Microservices Architecture are based on findings from the direction-setting activities.
• Summary of Current/Future State• Identified Gaps and Risks
• Foundational, Short-term, Mid-term and Long-term roadmap for building out your future-state architecture.• Quick Wins & Next-Step Recommendations
• Comprehensive executive summary of findings and recommendations• Readout presentation deck