Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Microservices needs and adoption strategy

831 views

Published on

Microservices needs and adoption strategy

Published in: Technology
  • Be the first to comment

Microservices needs and adoption strategy

  1. 1. Microservices needs and adoption strategy Sandeep R Singh IT Strategy and Enterprise Architecture Consultant sandeepsingh1976@gmail.com https://www.linkedin.com/pub/sandeep- singh/4/52a/136
  2. 2. 2 Why you need to adopt Microservices now Enablement through technologies (helps new startup companies and add competitions) • Cloud computing • High bandwidth availability • Open source Language and supporting frameworks • Stacks freedom! Recognition of business opportunities (threat due to competitions) • Accelerating business needs • Few inhibitor for global competitors • Reduction of entry barrier for niche competitors • Micro-Marketing to specific customers niches Barrier to overcome • Maintainability and clear ownership • build/test/deploy entire unit for small changes • Technology and stacks limits • Scalability challenges Benefits • 20-30% operational cost reduction • Ability to do daily deploys vs weekly to monthly • Able to build and deploy new features and capabilities in parallel within hours/days instead of months/years • Flexibility to quickly realign IT team with business priorities
  3. 3. 3 Benefits of adopting Microservices • Lower ongoing development and maintenance costs • Less personnel costs for administration and operations of the environment • Lower the licenses and maintenances cost on heavy weight middleware products • Rapid ‘time to market’ cycle of the solution to deliver on the most strategic business objectives • Ability to add updated from months/weeks to days to be competitive in market place • Be able to answer the right business questions at the ‘right time’ • Be able to innovate by building new ‘multi channel’ customer centric solutions • Able to meet Stakeholder/Customer Satisfaction • Highly scalable and parallel architecture • Ability to add, rollback and retire functionality • Increase reusability • Non- Destructive updates • Ability to do hundreds of independent update quickly • Decrease implementation cycles and time • Optimize existing investments in technology/applications • Less friction between development and operations teams • No meetings and no waiting • Every one has their own build • Reduce technology complexity • Streamline operational support and services Costs Value Enablement and Realizations Alignment Increase Agility
  4. 4. 4 Microservices adoption strategy Approaches to identify Microservice requirements Operational Shift Technology Shift Organization Shift Data architecture Shift Top-Down: Conduct business capability to process to system/application mapping to find best candidate for Microservices Bottom-up : Conduct existing ticketing and bug reports to find major capability/applications that went through change frequently which can be ideal candidate for Microservices Meet in the Middle: Conduct and categorize your applications/system into Gartner pace layer (Core/ Differentiation/Innovation systems/applications) to find best candidate for some Microservices SDLC Process IterativeWaterfall Agile R2/R1 (DevOps) Capability based DB Centralize DB Features based DB FederatedCentralize Capability based Features based Architecture Shift N-tier (Semi loosely coupled) 3/4 tier (Tightly coupled) SOA (Loosely coupled) Microservices (Flexible) BPMESB SOA API Docker Container Infrastructure PaaSOn- Premises Cloud Docker Container Application Mango DBOracle/DB2 Data Event Bus Team composition To achieve Agility To manage DB change

×