Raising Digital Quotient of highly regulated financial institution with Monolithic to Microservices Journey

1) What was problem?
Longer release cycle time, ever increasing code base, tightly coupled
functionalities of application making difficult to implement change, complex
organisation structure.
2) How we have approach towards problem: -
A) People transformation: - New organisational design where people are
responsible for making and running small set of Microservices. The services are
defined based on bounded context by levering Domain Driven Design.

B) Process transformation: -In order to identify the organisational process bottle
neck, End to end value stream mapping done and Improvements themes such as
change management, release management etc has been implemented.
C)Technological transformation: - New technologies, tools and practices adopted
that has helped in achieving engineering excellence by Automation,
Autonomation ,CICD, Infra as a code, cloud only infra , Microservices and API
led economy etc.

3) Our Approach towards Microservices :-
1. API led connectivity: - Composiblity of different system is the key for
Microservices experience and we can achieve the composiblity of
different system by leveraging API led connectivity approach. In this
approach, we will have system API, process API, and experience API.
System API takes cares of system of record underpinning the service,
process API takes care of business process underpinning the service and
Experience API is responsible for experience of consumer of services.
2. Elements of API design:- In our API design we have used domain
model , architectural standards , API catalogue ( experience , process ,
system) to identify development details, stub details , deployment
details, RAML specification ,data mapping ,back end system
specification and integration specification.

4) Client –Server Monolith application to Microservices application: -
1. Strangler pattern of Microservices: - In client –server monolith
application to Microservices application journey, we have used the
strangler pattern of Microservices. As we can see from architectural
diagram that we have put the dispatcher (API gateway, reverser proxy)
in front of monolith and directed our clients to it. The dispatcher also
acts as an API gateway and provides utility such as Authentication and
authorisation, logging and Auditing. The dispatcher is just a proxy to
endpoints exposed by monolith. We have refectored each domain into
Microservices and deployed them into Microservices platform.
2. Swagger: - We have used swagger to define, generate and Document
3. Caching as a service: - We have implemented cashing as service and we
have cached the static data of system API, experience API, and process
API. Cashing helps in improving the user experience.
4. Configuration of the API security context: - Our API Gateway exposes
API to consumers and protects services using the policy enforcement:
security policies.
5. Engineering excellence in Microservices landscape - We have achieved
engineering excellence by practicing CICD, Infra as code, automation
etc in Microservices landscape.
6. Other API design consideration: - a) Asynchronous event based
communication using the network for loose coupling between services.
b) Circuit breakers for isolating the failure of services c) Consumer
driven contract as way of service consumption.

5) When not to go for Microservices.

2 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/Structure of the Case Study

During the session , I will share case study based on our Monolithic
to Microservices Journey for highly regulated financial institution.

1) I will cover What was problem?

2) How we have approach towards problem ?

3) Our Approach towards Microservices

4) Different patterns of Client –Server Monolith application to Microservices application with specific focus on our applications' pattern that went for Microservices

5) When not to go for Microservices.

Learning Outcome

The participants will get the learning on various do's and don't of Microservices Journey in highly regulated environment . They will be able to get how to approach towards Microservices journey , Different patterns of Microservices journey , key elements that can make or break the journey and when not to go for Microservices.

Target Audience

Tech Arch, Technical Agile and DevOps coach , Engineering team ,CIO, technical leaders

Prerequisites for Attendees

Participants should have some understanding of micro services .

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • Prasad
    By Prasad  ~  1 year ago
    reply Reply

    Hi Ashok, 

    Thanks for the submission, I suggest your topic may be considered under Continous delivery theme. What I understood  from your proposal is how to enable business with frequent and early value..

    • Ashok kumar Pandey
      By Ashok kumar Pandey  ~  1 year ago
      reply Reply
      Thanks Prasad for your feedback, certainly continuous Integration and Continuous Delivery were one of prerequisites in the Digital transformation journey.In the session I want to cover the various aspects of microservices and it was done under the theme of becoming more digital.So I have put the session under digital transformation theme.


      On Nov 21, 2017 10:10 PM, "Agile India 2018" <info@confengine.com> wrote:
      Dear Ashok kumar Pandey,

      Your proposal Raising Digital Quotient of highly regulated financial institution with Monolithic to Microservices Journey has received a new comment from prasad-1

      Hi Ashok, 

      Thanks for the submission, I suggest your topic may be considered under Continous delivery theme. What I understood  from your proposal is how to enable business with frequent and early value..

      Visit https://confengine.com/agile-india-2018/proposal/5630#comments to respond to the suggestion OR simply reply to this email (Please make sure, you delete the previous comment's content from the email before replying.)

      Agile India 2018 Team
      You have received this important update from ConfEngine on behalf of Agile India 2018.
      Download ConfEngine's Mobile App to totally personalise your conference experience.
      If you are 100% sure, that this email was sent to you by mistake, please click here to unsubscribe from all future email updates from ConfEngine.
      • Ravi Kumar
        By Ravi Kumar  ~  1 year ago
        reply Reply

        Hi Ashok,

        Is there a draft version of the presentation that you can share? It will be interesting to see some insights on the following..

        • Various do's and don't of Microservices Journey in highly regulated environment
        • Different patterns of Client –Server Monolith application to Microservices application with specific focus on our applications' pattern that went for Microservices
        • When not to go for Microservices.





        • Ashok kumar Pandey
          By Ashok kumar Pandey  ~  1 year ago
          reply Reply

          Hi Ravi

          I do have outline that i want to cover in the session  and that i have already submitted as part of proposal. I am yet to start working on the deck. Will start once i get confirmation on my proposal being moved to next stage. 

          Please find my brief insights on the point that you have asked 


          Going for micro services journey without stream lining the organizational eco system such as controls and regulated mandates, governance structure, reporting needs, organizational infra setup , KPI’s, not empowering the team  and many more ….


          Going for incremental innovation approach in micro services journey

          Having organizational design in sync with micro services pattern

          Getting the infra that support the underservices journey and many more


           There are various Micro services patterns that can be used in-line with selected application/approach

          • Reporting intensive application
          • Std client-server based application
          • Applications that best suits for lift and shifts approach
          • Strangler pattern of micro-services etc……

                  Going for micro services is tradeoff that we have made in order to achieve the speed and agility and it requires

          1. Engineering excellence such as XP practices and tenets of DevOps
          2. A very good infra support
          3. Organizational designs, policies  that supports the ways of working required in micro services.
          4.  Not having awareness of what tradeoff we are making with micro services journey
          5. Many more ……

           So if we don’t above components than in that case it doesn’t make sense to move to micro services.


  • Archana Joshi
    By Archana Joshi  ~  1 year ago
    reply Reply


    In your proposal abstract you have highlighted 3 aspects - people, process and technology transformation. But your outline and learning outcomes are leaning heavily towards technology and micro-services. To make it a complete holistic Digital transformation journey that people can relate to I would recommend you to include pointers around people and process aspects too. Also for the reviewing team to make a decision, it will help if you can highlight your prior conference talks if any.


    • Ashok kumar Pandey
      By Ashok kumar Pandey  ~  1 year ago
      reply Reply

      Hi Archana

      In People aspects certainly,  I will be covering on organizational changes such as a change in roles and responsibilities, rewards,  enablement, performance management and soft aspects of OCM  that we have made to make our services self-sufficient. I will be covering how we have leveraged the VSM mapping to identify all the process bottleneck and related action taken in terms of streamlining all process under various themes such as release management, change management, incident management etc.

        Earlier I have been a speaker at AgileNCR 2016  and other local conferences. 

      please find the link of the presentation at https://www.linkedin.com/pulse/devops-only-means-achieving-organizational-agility-ashok-pandey/

      I will be also speaking on my proposed topic in in http://xpconference.in/2017XpConf/


  • Liked Prasad

    Prasad - A startup facilitated digital transformation journey of Europe's largest Insurance retailer

    schedule 1 year ago
    Sold Out!
    20 Mins
    Experience Report

    Large Insurance enterprises find difficult to renew and find new ways to transform their customer experience, improve operational process and find new business models. As an experiment they engaged an insure-tech startup to lead their digital transformation journey.. This case study is about a point of view, approaches, challenges and cultural surprises that we faced during this journey..

    The more we share more we learn!!

  • Liked Bernie Maloney

    Bernie Maloney - Wipeout! Make *New* Mistakes

    Bernie Maloney
    Bernie Maloney
    Agile Coach
    Persistent Systems
    schedule 1 year ago
    Sold Out!
    45 Mins

    Ever feel like the market moves faster than your marketing team? Or, wonder how flexible your finance (& leadership!) teams would really be if self-direction glitched and blew $1M? Organizations introduce Agile believing it will lead in part to greater responsiveness and resiliency. Yet, why do so many fail to achieve those outcomes?

    It isn’t just that they’re structured and operated by default along hierarchical lines rather than by design for iterative work. Achieving the full benefits of Agile comes from shifting the culture and mindset of a whole organization, sometimes as radically as encouraging it to “Make New Mistakes.” This very philosophy was a driver in the fastest division in HP’s history to reach $1B, a hardware division that was focused on manufacturing operations, with razor thin margins, and markets that changed 3x faster than the development lead time.

    Through a series of short stories and exercises, attendees will explore 5 practices from that business which led to roaring success. We’ll probe their parallels in Lean / Agile practice. With each one, you’ll briefly self-inspect the state of your own organization, as well as create a backlog you can use to adapt in your “real world” beyond the conference.

    Do you have, or want, a vision that takes you beyond high performing teams, to a high performing, resilient business? Come hear how you can help your organization shift from mechanics that “do” Agile, and walk away with a feel for what’s possible when not just development, but a whole organization surfs the flow of “being” Agile.

  • Liked Asheesh Mehdiratta

    Asheesh Mehdiratta - Self Managing Game Storm - How to form self designing teams

    90 Mins

    For transformations to be successful, typical Component teams are giving way to self managing, cross functional teams, organized by customer value (Feature Teams)!

    These Self-managing teams are the basis of Scrum, where the team has the authority to design, plan, and execute their task and to monitor and manage their work process and progress. The team rather than a (project) manager—has the responsibility of deciding how to work.

    But Self-managing teams do not just happen by chance. Instead they need the right environment. The organization is responsible for supporting the team development by creating the conditions needed for the teams to succeed and the real empowerment starts when the teams are 'self designed' from the beginning - which means that team members choose their teams to work!

    This workshop will showcase to the participants HOW they can form 'self designed' teams, and experience the joys of 'self organization'.

  • Liked Asheesh Mehdiratta

    Asheesh Mehdiratta - How do you rejuvenate your fading Communities of Practice?

    20 Mins
    Experience Report

    As part of organizational digital transformation journeys, CIOs are moving from hierarchical models to 'self organizing' Feature teams, in order deliver efficient and effective IT, but still need to retain the deeper functional expertise. Hence the growing importance of building and sustaining "Communities of Practices" (CoPs), as the traditional functional silos are broken down, with the transformation themes.

    But if you are a Change Agent responsible for the Transformation, you understand how challenging it is to nurture, and especially "sustain" these CoPs.

    So join my session, as I will share my experiences in nurturing and especially "sustaining" enterprise wide Communities of Practice (CoPs), while you recognize the key success and failure patterns in your own journey. In this session, you will learn techniques, tips and strategies that you can apply immediately, and in the end will walk away with practical advice on building "long lived" communities.

  • Liked Sunil Mundra

    Sunil Mundra - Be Alive, Be Agile

    Sunil Mundra
    Sunil Mundra
    Principal Consultant
    schedule 1 year ago
    Sold Out!
    45 Mins

    The Key challenge organisations are facing today is having to deal with the exponential rate of change which is happening in the external environment. The extent and pace of change is so disruptive that no organisation, regardless of age or size can take their competitive advantage or even their survival for granted.

    The main reason why organisations are struggling to change is that they are modeled as mechanistic or close-ended systems. On the contrary, all natural socio-economic systems essentially which are living systems have dealt with change very effectively since eternity.

    This talk is about infusing life into organisations. The speaker will highlight the key characteristics of living systems which enable them to deal with change effectively and also suggest actionable guidelines that will help leaders/influencers to bring their organisations to life. This approach will enable organisations to not only survive but thrive on change.

  • Liked Bernie Maloney

    Bernie Maloney - Bootstrap your Business Model - Business Agility on the Back of a Napkin

    Bernie Maloney
    Bernie Maloney
    Agile Coach
    Persistent Systems
    schedule 1 year ago
    Sold Out!
    90 Mins

    With every product we ship, we learn what we wished we’d known: what customers *really* wanted. What if you could gain those insights before beginning development? What if you could “unit test” a product idea? Or at a bigger level, what if you could “system test” your business idea/plan?

    Engineering teams are experiencing productivity gains of 30-300% when applying Agile and Lean practices and methods. These same Agile and Lean principles can be applied beyond engineering, to the business itself. Using a lightweight yet powerful tool, assumptions behind a business plan can be tested and iterated almost on-the-fly. With a hands-on exercise, attendees will learn how to build a map of any business ecosystem, and how to use it to check and iterate solution viability. Come experience the application of Agile to Business so you and your team can focus on your richest opportunities over chasing your competitor’s taillights.