Cloud design pattern using azure

Learn Cloud Design Patterns using Azure
Karthikeyan VK
Karthik_3030@yahoo.com
@karthik3030
https://blogs.karthikeyanvk.in

Enter Text
Why Cloud Design Patterns?
Availability & Resilience are hard in Cloud.
Performance and scalability are taken for granted in cloud.
Data management not a trivial Problem.

Enter Text
Why Cloud Design Patterns?
 It provides Off-the-shelf solution.
Automatically handles quality attributes.

Enter Text
What is Design Patterns ?
Design patterns are typical solutions to common problems in
software design.
Each pattern is like a blueprint that you can customize to solve a
particular design problem in your code.

Enter Text
Principles based Design

Enter Text
Why Principles ?
Not Technology Bound.
Helps decision-making process.

Enter Text
Solid Principles
S- Single Responsibility
O – Open Close Principle
L – Liskov Principle
I – Interface segregation
D – Dependency Inversion

Enter Text
Solid Principles
S- Single Responsibility

Enter Text
Solid Principles
O – Open Close Principle

Enter Text
Solid Principles
L – Liskov Principle

Enter Text
Solid Principles
I – Interface segregation

Enter Text
Solid Principles
D – Dependency Inversion

Enter Text
Cloud Design Principles
Design for self healing.
Make all things redundant
Design to scale out
Partition around limits
Design for operations- Deployment, Monitoring, Incident
response, Auditing

Enter Text
Cloud Design Principles
Design for Evolution.
Use the best data store for the Job
Build for the business needs. Think YAGNI

Enter Text
CQRS Pattern
Command Query Responsibility Segregation.
Command – Create/Update/Delete
Query – Select or Fetch

Enter Text
CQRS Pattern

Enter Text
Strangler Pattern
Incrementally migrate a legacy system by gradually replacing
specific pieces of functionality with new applications and
services.

Enter Text
Strangler Pattern

Enter Text
Pipes and Filters pattern
Decompose a task that performs complex processing into a series
of separate elements that can be reused.
The processing required by an application can easily be broken
down into a set of independent steps.
Keep your classes DUMB

Enter Text
Pipes and Filters pattern

Enter Text
Circuit Breaker Pattern
Handle faults that might take a variable amount of time to
recover from, when connecting to a remote service or resource.
Three States – Open, Half-Open, Closed State.
Use POLLY – nugget package to implement. Straight forward
solution.

Enter Text
Circuit Breaker Pattern

Enter Text
Compensating Transaction Pattern
Undo the work performed by a series of steps, if one or more of
the steps fail.
A compensating transaction is application specific.
Used in places where there is an eventual consistency
Solves the No-SQL world problem with different data store in
Microservices

Enter Text
Compensating Transaction Pattern
Used in places where there is an eventual consistency
Solves the No-SQL world problem with different data store in
Microservices

Enter Text
Static Content Hosting
Deploy static content to a cloud-based storage service that can
deliver them directly to the client.
This can reduce the need for potentially expensive compute
instances.

Enter Text

Enter Text
May not be suitable in application that needs to perform some
processing on the static content before delivering it to the client.
For example, it might be necessary to add a timestamp to a
document

Enter Text
Gate-Keeper Pattern
Protect applications and services by using a dedicated host
instance that acts as a broker between clients and the application
Validates and sanitizes requests, and passes requests and data
between them.

Enter Text
Gate-Keeper Pattern

Enter Text
Event Sourcing Pattern
Instead of storing just the current state of the data in a domain,
use an append-only store to record the full series of actions
taken on that data.
The events are persisted in an event store that acts as the system
of record (the authoritative data source) about the current state
of the data.

Enter Text

Enter Text
Apache Kafka, Service Bus, Queue/Blob Storage

Enter Text
Sharding Pattern
Divide a data store into a set of horizontal partitions or shards.
This can improve scalability when storing and accessing large
volumes of data.

Enter Text
Sharding Pattern

Enter Text
Sidecar Pattern
Deploy components of an application into a separate process or
container to provide isolation and encapsulation.
Applications and services often require related functionality, such
as monitoring, logging, configuration, and networking services

Enter Text
Sidecar Pattern

Enter Text
Sidecar Pattern
SSL Termination by application gateway.
Health monitoring is deployed as service in the host to be used
by multiple services.

Enter Text
Anti-Patterns

Enter Text
Why Anti-Patterns ?
Application behaves well during all types of testing. But behaves
badly in production.
 The development team is then faced with two questions:
• Why didn't this behaviour show up during testing?
• How do we fix it?

Enter Text
What is Anti-Patterns ?
Anti-Pattern is a common practice that is likely to cause problems
when an application is under pressure.
It's very difficult in a test environment to simulate real users.

Enter Text
Busy Database Anti-Pattern
Offloading processing to a database server can cause it to spend
a significant proportion of time running code.
Remember stored procedures and triggers !

Enter Text
No Caching Anti-Pattern
Repeatedly fetching the same information from a resource that is
expensive to access, in terms of I/O overhead.
Also think about stale data
Remember the expiring cache. Absolute or Sliding expiration.
Monitor your application and queries

Enter Text
Chatty I/O Anti-Pattern
The cumulative effect of a large number of I/O requests can have
a significant impact on performance and responsiveness.
Packaging the data into larger, fewer requests
Problem seen in improper domain division in Microservices.

Enter Text
Improper Instantiation Anti-Pattern
It can hurt performance to continually create new instances of an
object that is meant to be created once and then shared.
Think about singleton pattern.
Always reuse System.Net.Http.HttpClient or any connection
related broker classes

Enter Text
References
@karthik3030
• https://code-maze.com/liskov-substitution-principle/
• https://medium.com/@domagojk/patterns-for-designing-flexible-architecture-in-node-js-cqrs-
es-onion-7eb10bbefe17
• http://cloudgirl.tech/data-partitioning-vertical-horizontal-hybrid-partitioning/
• https://docs.microsoft.com/en-us/azure/architecture/patterns/

Enter Text
Networking and more
@karthik3030
• https://www.facebook.com/aspiringDotnetArchitects/
• https://www.meetup.com/Chennai-Microsoft-Azure-User-Group/
• https://www.youtube.com/channel/UCJxa58lDcDj4tYQIHh7ORxA

Enter Text
@karthik3030
Thank you
/Q&A

Cloud design pattern using azure

More Related Content

What's hot (20)

Similar to Cloud design pattern using azure (20)

More from Karthikeyan VK (20)

Recently uploaded (20)

Cloud design pattern using azure

Editor's Notes