11
Keynote - Cloud Experience sopan shewale

Cloud experience

Embed Size (px)

Citation preview

Page 1: Cloud experience

Keynote - Cloud Experience

sopan shewale

Page 2: Cloud experience

Web Application – Traditional Architecture Web Application -Issues with Traditional Style Web Application-Cloud Enabled Clouds Short History-initializers Key Elements for Cloud Success-Automation Key Elements for Cloud Success-Monitoring

and Recovery Big Data – kind of part of cloud

Agenda

Page 3: Cloud experience

Web Applicationtraditional architecture

Application

Databases

Web Servers

Page 4: Cloud experience

Web ApplicationIssues with Traditional Style

Application

Databases

Web Servers Application Development Technology

Application Hosting Deployment Upgrade Patches/

Customization Systems

Administration OS Administration Hardware LAN/WANResources – People

Page 5: Cloud experience

Web ApplicationCloud Enabled

infrastructure

storage platform

Application

Resources: Adopt new Style Developers Systems Administrator-

with new Cap , called DevOps

Scalability – elasticity Performance Cost –Metering Self service – log/data Auto-Patching Helps focus on Business

Page 6: Cloud experience

Clouds Short History-initializers

Year 1999: Salesforce.com , Delivery of applications via website

Year 2002: Amazon , started Amazon Web Services, storage, computation Human/business intelligence

Year 2006: Amazon, Elastic Compute Cloud Year 2009: Google Inc, Google Apps. Developing

Applications made easy

Page 7: Cloud experience

Key Elements for Cloud SuccessAutomation

Deployment: Stamping of new Customer Environment should be automated/Easy (in one or two manual steps)

Day to Day maintenance: Least interaction with Developers, other stake holders. Only DevOps able to manage (in automated fashion)

Patch Management, Customization: Least manual steps Restore/Copy /DR- Automated way

Page 8: Cloud experience

Key Elements for Cloud SuccessMonitoring and Recovery

SLA’s – Four or Five 9’s (four nines is 99.99% year uptime)

API’s opened in Application itself – to suggest the feature is up and running In case of issues – suggested actions to repair

Alerts – in case of any non-expected results Could be via emails, SMS, pagers

Failover actions – recover mechanisms integrated with monitoring infrastructure

Page 9: Cloud experience

Big Data Splunk - commercial Logstash – Open Source

How does this stuff works? Helps find trends/build BI on -Structured data,

Unstructured Data Helps enrich Unstructured Data (especially on log

files) by adding meta-data, build Applications using those meta-data

Nothing but search – on log files

Big Data – kind of part of cloud

Page 10: Cloud experience

Reading-Novels