In this session we will explore how Cloud Native technologies require us to re-think the way businesses create and scale modern digital solutions. We will explore the trends that are driving the adoption of these technologies and the key use cases for their application. Most importantly, we will uncover the business problems that these technologies are most effective at solving. While many tools exist for Containers, Microservices Architecture, DevOps, and Continuous Delivery processes involved in Cloud Native development, we aim to provide best practices and guidance on how to approach these business problems when solutioning using the Microsoft Azure platform.

1. Webinar: Thinking In Cloud-Native
Speaker: Ashish Patel, CTO, Architech
www.linkedin.com/in/ashishipatel/
Microsoft Cloud Digital Series
Learn online at your pace about AI, Analytics, Applications,
IoT, Migration, Modernization and more, all powered by
the Cloud
www.aka.ms/CloudDigitalSeries

2. WHY
CLOUD-NATIVE?

3. worried about
disruption
convinced they're
too late to start
BUSINESS AND DIGITAL
TRANSFORMATION: THE CHALLENGES OF A CIO
87
%
44-59%

4. TREND OF APPLICATION DEVELOPMENT IN ENTERPRISES
+60
%
Increase in application
development from 2018 -2019
Time to market: 6 months

5. WHY CLOUD-NATIVE
MATTERS TO A BUSINESS
Grow and capture
new customers
Users want new
features, faster
Speed and risk
mitigation

6. Speed Freedom Confidence
An enabler to digital transformation and a path to
velocity with risk mitigation

7. WHAT IS CLOUD-NATIVE?
A modernized
set of technologies
A different
approach to
managing teams
Building &
managing software

8. Tighter integration
across build, deliver,
run and manage
Smaller
pieces
More granular
visibility control
CLOUD-NATIVE ARCHITECTURAL PRINCIPLES
Portability

9. THE FOUR PILLARS THAT MAKE UP CLOUD-NATIVE
What we build
How we deliver and update
How we build
How we manage all of it
Microservices Containerization
Continuous Delivery Processes DevOps

10. MICROSERVICES
What we build

11. MICROSERVICES – WHY?
Compared to traditional application
development, microservices are:
Easier to build,
debug, and test
Designed for
automation
Faster to scale Mapped to
domain expertise

12. Scaling
visibility
Right-sizing
granularity
Delivering to
legacy environments
MICROSERVICES - CHALLENGES

13. Microservices turn a
traditional application
(often called a monolith)
into a collection of
smaller, discrete and
distinct services.
MICROSERVICES – WHAT ARE THEY?

14. CONTAINERIZATION
How we build

15. CONTAINERIZATION– WHY?
Optimize resource
efficiency
Simplify
administration
Consistent build
environment
Write once, run
anywhere
Containers simplify our ability to build and deliver cloud-native applications,
writing without worry about dependencies and infrastructure constraints.

16. Containers
are faster
More
flexible
More
reliable
CONTAINERIZATION VS VIRTUALIZATION

17. A bundle of microservices delivered as an application
inside an infrastructure-neutral,
self-contained software micro-environment.
WHAT IS CONTAINERIZATION?

18. • As with microservices,
orchestrating containers
takes new tools and
strategies. The clear leader
is Kubernetes.
• Manages containers in pods
• Scales pods through
deployments
MANAGING CONTAINERS - ORCHESTRATION

19. Microservices &
Containerization
Case Study

20. CLIENT
BEFORE
AFTER
Siloed, slow, less visible
Modernized, high-performing,
more valuable
BEFORE
AFTER
Development team balancing both
application and infrastructure
details
More time to focus on
development,
faster and safer to deploy
CONTAINERIZATION MICROSERVICES
Canada’s busiest coal
export terminal

21. CONTINUOUS
DELIVERY PROCESSES
How we deliver and update

22. CONTINUOUS DELIVERY PROCESSES – WHY?
Reduces costs
through
automation
Makes the most
of your software
expertise
Makes more
efficient use of
your resources

23. A CONTINUOUS DELIVERY PROCESS

24. SPEED VS. CONTROL – IS CD SAFE?
Quality can be managed
through integrated testing
Risk mitigation for
elegant fallbacks

25. DEVOPS
How we manage all of it

26. You can’t measure (or improve)
what you don’t see
Faster
Defect fixes
More
Stability
Quicker time
to market
Less
friction
More stability Faster defect
fixes
DEVOPS – WHY?

27. PUTTING IT ALL TOGETHER

28. People
People
People
DEVOPS CHALLENGES

29. DevOps & CI/CD
Case Study

30. BEFORE
AFTER
Costly, hard to manage pipelines,
many 3rd party tools
Fewer tools, faster administration
through native tools and Kubernetes
Orkestra SCS is a Canada-based
supply chain solutions company
that optimizes, streamlines, and
consults for consumer supply chains.
CLIENT – ORKESTRA SCS

31. THE FOUR PILLARS THAT MAKE UP CLOUD-NATIVE
What we build
How we deliver and update
How we build
How we manage all of it
Microservices Containerization
Continuous Delivery Process DevOps
Speed Freedom Confidence

32. Questions?
Learn more about the benefits of
Kubernetes from our white paper
sales@architech.ca
www.linkedin.com/in/ashishipatel/
architech.ca
An enabler to digital transformation and a path to
velocity with risk mitigation

33. Next steps in your learning journey
Register for the next webinar at: Register for in-person technical learning or a
hands-on experience at:
For more learning resources, please visit:
www.aka.ms/CloudDigitalSeries www.aka.ms/MicrosoftTrainingDaysCanada www.aka.ms/MSLearn
Microsoft Cloud Digital Series
www.aka.ms/AzureHands-OnLabs

34. Thank You
70 Bond St., Suite 500
Toronto, ON, Canada
M5B 1XB
P: 416.607.5618
F: 416.352.1768
www.architech.ca
©2020 Architech. All Rights Reserved.