These research slides provide insights into the critical issues involved in handling application- and infrastructure-complexity in ever-changing hybrid multi-cloud settings. Torsten Volk, Managing Research Director at EMA, and Jasper Paul, a Principal Product Manager at ManageEngine Site24x7, explore:
The Anatomy of Complexity: Understand and escape the complexity trap of distributed cloud native applications.
Monitoring and Metrics: Examine approaches for effective monitoring of resource utilization and performance as key components of complexity management.
AIOps: Examine the capabilities of AIOps.
FinOps Strategies: Explore frameworks and best practices for efficiently managing your cloud's financial operations without compromising on performance, resilience, or security.
Case Studies: Gain insights from real-world instances where companies have successfully mitigated the complexities and risks associated with distributed microservices architectures.
How to Troubleshoot Apps for the Modern Connected Worker
Navigating the Complexity of Distributed Microservices across AWS, Azure, and Google Cloud
1. Navigating the Complexity
of Distributed Microservices
across AWS, Azure, and
Google Cloud
Torsten Volk
Managing Research Director
Enterprise Management Associates (EMA)
Jasper Paul
Principal Product Manager
ManageEngine Site24x7
5. Unfiltered
Complexity
Same data as title page:
2,932 Posts from
StackOverflow
25 out of 1040 problem
categories
Boxes sized by ‘number of
searches’
Result:
‘Infinite’ combinations
6. Modern App
Stacks Are
Complex
12 Layers (pink)
X
4-7 Components per
layer (blue)
X
Multiple choices per
component
= Complexity
And that’s just one
microservice
7. Distributed Apps: App Stack X 25
1. 25 codebases instead of one
2. 25 stacks instead of one
3. 25 release schedules instead of one
4. API calls instead of direct function call
10. Example: Networking Telemetry Data from One Microservice
Disjointed telemetry
data from the
networking layer
Data points are not
connected to
application code
or business
processes
And remember:
There are 11 more
layers
11. Data Driven Decision
Making Needs
Context
Critical Context Factors
- Who will be impacted?
- What is the extent of the
impact?
- What is the cost?
- How does all this affect key
business metrics?
12. Connecting the
Dots Between
Technology and
Business Is Key
The impact of each factor
has to be understood for an
observability platform to be
able to optimize
performance, resiliency,
cost, compliance, and
security.
15. 8 Ways of How AI Can Help Connecting the Dots
Between Infrastructure, Application, and Business
16.
17. Observability + FinOps
Challenges
-Long time to parse Cloud bills
- Unable to identify cloud cost
leakages
- Difficult downloading Reports
- Multi-currency support at
Business Unit level
Actions
-BU visibility of cloud
-Auto remediate with IT
Automation with cloud monitoring
-Right size recommendations
-Integration with overall
ecosystem
18. Key Takeaways
Do not allow gaps in your telemetry data. Continuously scan for new
but unmonitored devices and services.
Always capture, analyze, and store data within its context.
Leverage AI for automatic root-cause analysis and optimal decision
making. Observability platforms need to deliver actionable insights
instead of disconnected alerts and dashboards.
Leverage FinOps to collaboratively optimize cost without sacrificing
resiliency, compliance, performance or security.