Patterns for Building High Performance Applications in Cloud - CloudConnect2012
•Als PPTX, PDF herunterladen•
0 gefällt mir•1,077 views
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (11)
Ähnlich wie Patterns for Building High Performance Applications in Cloud - CloudConnect2012
Ähnlich wie Patterns for Building High Performance Applications in Cloud - CloudConnect2012 (20)
Mehr von Munish Gupta
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Patterns for Building High Performance Applications in Cloud - CloudConnect2012
- 1. Patterns for Building High Performance Applications in Cloud Munish K Gupta 1
- 2. Who am I? Twitter - @write2munish • Current Avatar • Practice Lead – Architecture for High Performance Applications (AHiPA) @ Wipro Technologies • Work with lot of open source stuff – Play Framework, Akka, Scala, mongodb, redis, LAMP stack • Previous Avatar • Chief Architect for ideaken.com • Worked @ Wipro, Sapient, MindTree and Siemens • My Blogs • http://www.techspot.co.in • http://www.akkaessentails.in 2
- 3. Expectation(s) • This session will not solve your problems ! • My goals are • To make you think harder about your problems • Help you evaluate possible solutions • Agenda • Patterns for building High Performance Applications 3
- 4. Patterns for building High Performance Applications Reduce Latency Scalability High Availability Application requirements 4
- 5. Scalability No Load Balancing vs Load Balanced Stateful vs Stateless Synchronous vs Asynchronous 5
- 6. Reduce Latency Simplify – Not too many moving parts, simple application tiering SOA ESB Host closer to Customer – choose Cloud Vendor wisely Bring data close to customer – Cache 6 (browser, edge, webserver, data cache)
- 7. High Availability Master - Master Replication mode Master-Slave replications mode Write Read Write Update Read Master - Slave Master Fail Over 7
- 8. High Performance Applications – Impact Factors • Topology of the Solution • Single Point of Solution Failure(s) Reduce • Chosen Product Latency Architecture Stack • Product Integration Scalability Strategy • Application Design • Choice of Application Frameworks Architecture • Standards Enforcement High • Build & Release Availability • Hardware Choices made • Hardware/Software Sizing Application requirements Deployment • System Configuration(s) Architecture • Hosting Environment • Application/System Monitoring • Capacity Planning 8
- 9. Summary Service • Patterns based • Scalability • Load Balancer Uses • Asynchronous Internet Scalable Technologie and Elastic • Stateless s • Reducing Latency Cloud Attributes • Bring data closer to end user • Do not have too many moving parts • Host your application close to users! • High Availability Metered Shared • Fail Over usage • Redundancy You can read all the books in the world about riding a bicycle, but you will not be able to ride one until you get on it and fall off a few times. 9
- 10. Munish K Gupta write2munish (at) gmail dot com Twitter @write2munish Blog(s) www.techspot.co.in 10 www.akkaessentials.in
Hinweis der Redaktion
- The below and following notes on the template slides are to guide you only. In your final presentation, you may delete these notes and add relevant notes if any.Title slide:Title– should not exceed beyond 3 lines, font size 30-34, Arial Bold (Font size for the title of the PPT can vary between 30-34, Arial, Bold depending on the amount of text, however should not be smaller than 30 font size)Name should not exceed beyond 1 line, Designation; font size to remain at 16, Arial normalPlease keep the title slide simple, just the logo, title and name and designation to appear. No other graphic elements or any design, photograph, image can be added to this slide, alignment to remain the same
- Blank slideyou may use this to insert or show screenshots etcIf content is added in this slide you will need to use bulleted text