Applying Architectural Patterns For The Cloud

Applying Architectural Patterns forthe Cloud:Lessons Learned During Pattern Mining andApplicationRalph Retter (Daimler TSS GmbH)ralph.retter@daimler.comChristoph Fehling (University of Stuttgart, Germany)

ProblemWe need to do Cloud Computing!multi-tenancyelasticitydynamictoolingWe never did it like this business modeldata centeravailabilityplatformIaaShave alwaysthissharingbefore!hybridWe SaaSresourcepublic done it likecollaborationcost SLApay-per-useWhere will we end, if everybody did privateit like age2

Cloud Computing Architectural PatternsA Structured Approach Structures the Problem using a Pattern Language Focus: Application Architecture for the cloudpatterns mined at different enterprises by different people!3

The ReasonWhy did we mine the patterns?4

We need to do Cloud!Typical Resulting Questions "Which cloud infrastructure (provider) is the right one for our enterprise?“ "Is this application suitable for the cloud?" "Why isn't it as easy to deploy an application in our data center as it is todeploy a sample application in my favorite public cloud?“5

What Happens Next Business ProcessApplicationPlatformInfrastructurebottom up approach6

Typical Result of Bottom UpBusiness ProcessBusiness ud Infrastructure7

What You Really WantBusiness ProcessBusiness ProcessCloud reCloud Infrastructure8

The ApproachWhat we learned by mining and applying the patterns, and what they aregood for!9

Real Requirements ! We need to do Cloud! Example requirements: Deal with dynamic load patterns without provisioning for peak-load save money! Make application deployments easier and faster save time through standardization! 10

Better Questions(Requirement Driven)1. Which of my business processes benefit from cloudproperties of underlying applications? dynamic load patterns Pay-per-use Self service required?2. Which applications drive these business processes andcan they deal with: Resource sharing / pooling Elasticity as a result of requirement for dynamic load patternsand pay per use?3. What (Cloud) Infrastructure and platforms are neededto support these applications?11

Top Down Approach Business ProcessApplicationPlatformInfrastructuretop down12

How To Use the Patternsillustrative example - the coffee shop13

Requirements of Illustrative Example: Functional Make coffee-related specialities and sell them to walk-in customers Non-functional requirements Deal with varying amount of simultaneous customers according tothe time of the day Maximize order throughput! Keep lines as short as possible14

Traditional Small Coffee Shop ArchitectureCoffee ShopCoffeeMachineBlenderGuy who Takes order Makes drink Takes cashYou15

Cloud-Based Bigger Coffee Shop ArchitectureCoffee ShopCoffeeMachineBlenderGuy who Takes order Makes drink Takes cashCoffee ShopCoffeeMachineBlenderGuy who Takes order Makes drink Takes cashYou16

Example: Cloud Native ApplicationCoffee-Shop ArchitectureElastic ComplexBusiness LogicComplex processingOrder (cup withcorrelation token)Message QueuingData StorePick-up counterEnjoy!Pick upWith correlationtokenCashier counterYummy SweetsElastic Web Frontend / AppsNotificationWith correlationtokenCorrelationToken(name)Cash nameAdapted from: Gregor Hohpe: Your Coffee Shop Doesn‘t Use Two-Phase Commit, IEEE Software 2005„invoice“Youorder17

Cloud-Native Bigger Coffee Shop ArchitectureCoffee aBaristaOrder QueueOutput QueueCashierYou18

Example Pattern: 3-Tier Cloud Native ApplicationreadRequired Services @ Cloud ProviderElastic Load BalancerElastic PlatformHigh-Available MessageOriented MiddlewareElastic InfrastructureElastic QueueScalable, High Available DataStore19

Requirements on Cloud Platform / InfrastructureRequirements resulting from Application Designvs.Environment-basedavailabilityNode-based availability20

Some More Lessons Learned Moving to virtualized Machines is not Cloud! Even if you automate it! Consider environment-based availability and dynamic horizontal scaling Use highly available messaging and storage platform offerings Make sure you are aware of the CAP Theorem and it‘simplications– Decision to trade towards higher availability and eventualconsistency has impact on business processes! Modularization! Make sure you can scale different parts of your system according totheir workload Seperate short-running transactions with the user from long-runningtransactions in backend Use asynchronous messaging and compensation-basedtransaction models in backend Resource Sharing!21

Top-Down Approach Pattern MapFundametalArchitectureComposite(Hybrid) grationApplication ComponentsCloud Native ApplicationsApplicationDevelopment &ManagementInfrastructure & Platform Offerings (Network, Compute, Storage) & their Properties22

Pattern FormatTitle Unique NameIntent Purpose and GoalIcon to use in DiagramsDriving QuestionContext: When is this pattern applicableSolution: Brief escription how problem is solvedSketch: Big Picture how Pattern worksResult: Detailed description of solution and itsresultsRelated Patterns: Links to other patternsKnown Uses: Publicly Accessible Services,Solutions, Descriptions that implement thepattern23

Cloud Computing Patterns - Summary Composite Cloud ApplicationsCloud OfferingsCloud Computing FundamentalsCloud ApplicationManagementCloud Application Architectures Not all Cloud Computing Patterns are new!Many existing patterns can be transferred orsimply used in the area of cloud computing. http://cloudcomputingpatterns.orgComposite Cloud Applications Common use cases Example ApplicationsCloud Application Architectures Building cloud applications Integrating different cloudsCloud Offerings Processing, storage, andcommunication functionality Behavior of cloud offerings Provide runtime functionalityCloud Computing Fundamendals Cloud Service Models Cloud Types Application Workloads Characterize the environmentCloud Application Management Elasticity, resiliency, updates etc. Automation of management24

etter@daimler.com25

Cloud Application Management Elasticity, resiliency, updates etc. Automation of management. Composite Cloud Applications. Cloud Computing Fundamentals. Cloud Offerings. Cloud Application Architectures. Cloud Application Management. Not all Cloud Computing P atterns are new! Many existing patterns can be transferred or