This document discusses the challenges of delivering microservice applications in enterprises, focusing on issues like changing deployment patterns, service dependencies, and the risks of adopting new technologies. It emphasizes the importance of using the right tools to manage complexities and recommends maintaining flexibility in technology implementation. Despite the advantages of microservices, the author suggests that monolithic architectures may still be more suitable for simpler applications.

1. #DOPPA17
Microservice | Challenges in delivering microservice
applications in enterprise
9th September 2017 Sathish Kanth

2. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for
social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
What Are Microservices?
Autonomous Service
Encapsulates a scenario organized around business capabilities
Contain code plus state
Independently versioned, deployed and scaled
Interact with other microservices over well defined interfaces
Uses protocols such as http/rest
Remains consistent and available in the presence of failures

3. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for
social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Simple Architecture explaining both Application types

4. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for
social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Challenge 1:
How to handle changing deployment patterns?
 Delivery-Management complexity moves from within Application itself to
external relationship between services.
 Standardized Platforms and decentralization of Data Management.
 CI and CD pipelines.
 Phased Rollout
 To make best of microservice, a single overview of deployment
dependencies and configuration is needed, with deployment tools handling
multiple deployment simultaneously. This allows microservice deployment
tool to offer speed and efficiency.

5. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for
social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Challenge 2:
How to deal with dependencies between services?
 Track dependencies – More the component, more the complexity. A missed
dependency fails the system and difficult to track the source of the issue.
 Cascading failure effect
Netflix uses Chaos Monkey to force failure in the system
 Monitoring and Logging – Alerts
Threshold limits
Response time at endpoints
 With plenty of manual task to handle as we approach to production, its
important to use tooling that can support manual activities too.

6. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for
social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Challenge 3:
How to avoid getting stuck with wrong implemented
technology?
 Buzz word Docker – Docker is a great solution for many situations but are we
sure of its drawback
 Reality of committing new technology is a gamble – Key factor “Changing
Market”
 Need to ensure tooling and process work seamlessly regarding the
underlying technology.
 Keep implementation options open and flexible until a mature solutions is
derived.

7. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for
social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Microservices are not a Panacea

8. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for
social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Take Way:
 Even though building complex applications is inherently difficult, A
Monolithic architecture better suits simple, lightweight applications.
 DevOps need to be adopted
 Require sufficient tools to handle the dependency and complexity
 Conway’s Law…….