• Like
  • Save

Cloud elements Building Cloud Applications Faster

  • 884 views
Uploaded on

Building cloud SaaS applications faster and at 1/3 the cost! Spend more time developing your unique SaaS functionality & less time integrating common services.

Building cloud SaaS applications faster and at 1/3 the cost! Spend more time developing your unique SaaS functionality & less time integrating common services.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
884
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
2
Likes
5

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Title oneBUILDING CLOUD APPS FASTER Title twoFebruary 7, 2013 Cloud Elements Confidential 2013
  • 2. WHAT’S DRIVING THE CLOUD? Cloud Elements Confidential 2
  • 3. CLOUD ADOPTION IS DRIVEN BY NEW MARKETOPPORTUNITIES NOT JUST COST EFFICIENCIES Source: 2012 Future of Cloud Computing Survey, North Bridge Ventures Cloud Elements Confidential 3
  • 4. Cloud Elements Confidential 4
  • 5. WHAT’S A REAL CLOUD APP? Cloud Elements Confidential 5
  • 6. 5 CHARACTERISTICS OF CLOUD-OPTIMIZEDAPPLICATIONS Multi-tenancy Self-service provisioning Elastic & metered resource consumption Services-based integration Accessible from any device Cloud Elements Confidential 6
  • 7. WHAT’S THE LANGUAGE OFTHE CLOUD? Cloud Elements Confidential 7
  • 8. WHAT’S THE LANGUAGE OF THE CLOUD? Open RESTful APIs Rule the Cloud REST APIs loosely couple IaaS, PaaS and SaaS services Participate in the “API Economy” − Use the same service calls internally as externally − Low friction access; well documented API calls Build applications by connecting services Cloud Elements Confidential 8
  • 9. THE AMAZON MANDATE (PER JEFF BEZOS) All teams will henceforth expose their data and functionality through (API) service interfaces. Teams must communicate with each other through these (API) interfaces. There will be no other form of inter-process communication allowed The only communication allowed is via service interface calls over the network. All service interfaces, without exception, must be designed from the ground up to be externalizable.No exceptions. Anyone who doesn’t do this will be fired. Thank you; have a nice day! Cloud Elements Confidential 9
  • 10. THERE’S A “SERVICE” FOR THAT! Find SaaS services you can leverage in building your app Glue them together through REST APIs Evaluate the API when evaluating vendors Focus your resources on your unique functionality; not on building services that already exist Case Study: SaaS Distribution Application − Customer Management: SugarCRM (salesforce.com) − Billing: jBilling (Zuora) − Payments: Authorize.net − Email Messaging: SendGrid − SMS Messaging: Twilio − Customer Service: ZenDesk (GetSatisfaction) − Custom: User Interface, Order Entry, Quoting Cloud Elements Confidential 10
  • 11. WHAT PLATFORM SHOULD IBUILD ON ... IaaS or PaaS? Cloud Elements Confidential 11
  • 12. WHAT IS PLATFORM-AS-A-SERVICE (PaaS)? A “cloud-aware” application development and deployment environment An abstraction layer between your cloud application and your Infrastructure-as-a-Service (IaaS) provider Fundamentally provides elastic scaling of your application Deployments include public, private and hybrid cloud configurations Cloud Elements Confidential 12
  • 13. EXAMPLE: PaaS SERVICES Cloud Elements Confidential 13
  • 14. EXAMPLE: PaaS & IaaS SERVICES Cloud Elements Confidential 14
  • 15. PRIMARY BENEFITS of PAAS Lower Development Cost (30%+) Lower Deployment and DevOps Costs (Nearly Eliminate) Application Portability (depending on the PaaS) Cloud Elements Confidential 15
  • 16. CLOUD APPLICATION ARCHITECTURE WITH PAAS Cloud Elements Confidential 16
  • 17. PAAS OFFERINGS Services: Heroku, AppFog, CloudBees, Standing Cloud, Eucalyptus, Force.com, Azure, Tier 3, Cloud Foundry, Apprenda … Open Source: Cloud Foundry (VMware), OpenShift (RedHat) and Eucalyptus Amazon Web Services (AWS) offers many PaaS-like services − They do not offer an abstraction layer between these services and their IaaS platform − 3rd party PaaS providers such as AppFog and Eucalyptus provide deployment options to AWS OpenStack & CloudStack are primarily IaaS platforms; not PaaS Cloud Elements Confidential 17
  • 18. CLOSING THOUGHTS Don’t just virtualize; optimize Develop on a PaaS Platform not an IaaS Platform Architect before you build ... not after “Integrate First” ... Build Second Service based design; Same APIs internally as externally Cloud Elements Confidential 18
  • 19. Cloud Elements Confidential 19
  • 20. NEXT DENVER All-THINGS-CLOUD MEET-UP Date: March 14th http://www.meetup.com/All-things-Cloud-PaaS-SaaS-PaaS-XaaS/ Cloud Elements Confidential 20
  • 21. MORE INFORMATION Blog: www.cloud-elements.com/blog/ Twitter: @cloudelements1 Email: gary@cloud-elements.com Cloud Elements Confidential 21
  • 22. 5 EVALUATION CONSIDERATIONS1. Does the PaaS support my preferred list of services? − Application runtimes − Development frameworks − Database services2. Does the PaaS support my deployment preferences? − Public, Private and Hybrid3. Is application portability important? − Multi-cloud or single-cloud? − Open source available?4. What are the value-add services? − Marketplaces − Partner ecosystem − SaaS-type services5. Does it fit my application strategy? − e.g., developing on services such as Azure (Microsoft) and Force.com (salesforce.com) can drive strategic relationships these vendors − e.g., you want to deploy your application to private clouds and open source provides that alternative Cloud Elements Confidential 22
  • 23. Cloud Elements Confidential 23