Microservices - S1E2 - Vision

Microservices - S1E2 - Vision

Recap

Vision

We fail more often in microservice migration because we treat it as "Technology Architecture". No, It is an Enterprise Architecture. That means, it has to address following TOGAF ADM aspects.

No alt text provided for this image
https://www.opengroup.org/togaf

There are tools available like Archimate (UML Diagrams) which can help us to derive Requirements for the migration program. However, it is a wider topic and we will scope it out. We will use some of the Techniques to address the Requirement in hand.

Identify Decision Makers = Drivers

  1. Non Technical Decision makers who care about Value, Revenue and Time to Market (Stakeholders, Business...).
  2. Technical Decision Makers who care about Design, Roadmap, Delivery and Maintenance (Architects, PMO...).
  3. Most importantly be clear on the values that you expect. This is the motivational factor that made you drive this project and as long as it is alive, the program will be successful.

Identify Value, Revenue and Time to Market

Value

Each decision maker has got one or more perspective on the product in question. You need to identify the motivation and highlight the value. In fact, you as an architect, should come up with the values that will motivate the respective drivers in most of the migration projects.

For Ex: Operational Cost
To Business => I can deliver solutions faster since it avoids X,Y,Z operational costs.
To Stakeholder => The new system can save $ABC since we don't have to spend on X, Y, Z operations.

Revenue

It is not always about operational cost. Showcase the new business opportunities that gets enabled when we migrate to microservices. Read case studies and success factors that companies achieved while adopting to the microservice architecture. Identify the area's which are restricting you to grow the revenue and present how the new system solves the same.

For Ex: Domains are separated by design
To Stakeholder => We can introduce new product faster since they do not affect my delivery system.
To Business => I can provide better analytics over the customer actions which will help you target VIP customers at right time.

Time to Market

We should have a solid migration plan in place.

We cannot achieve everything over a day. However, we can make it better every day. We will get there eventually 😊

Be clear on minimal product that delivers the value (Minimum Viable Product (MVP)). Design initial and target architecture. Follow Façade approach to achieve successful migration.

No alt text provided for this image


Nice dialog from Avengers Part 1. But even they failed because they had no plan and team coordination.



Summary

  1. Identify the driver's perspective on the system to derive Value and Vision.
  2. Identify new opportunities that get enabled when we migrate.
  3. Consolidate Values and Opportunities to showcase the Revenue.
  4. Prepare a roadmap that is practical and fits in plan with minimal cost.
  5. Adopt MVP based deliverables.

Next:


To view or add a comment, sign in

More articles by Acharya Suhas TJ

  • Microservices - S1E3 - Design

    Introduction In the previous episodes, we discussed Vision aspect. The current article talks about more on how do you…

  • Microservices - S1E1 - Introduction

    I want to Migrate from "Monolith" to "Microservices" Team now a days come up with an architectural proposal to Business…

Others also viewed

Explore content categories