From DevOps to NoOps: 10 cloud services you should be using


Published on

A couple of years ago building an application meant building the infrastructure to support the application. Typically this entailed installing a database, an app server and often a messaging server and email server; all tedious preamble for actually building an application. Now you have free access to these infrastructure services on the web, but which ones should you use.

This session will pick 10 services available today such as MongoHQ, Twilio and DropBox. With no infrastructure for you to set up for your application you can now start coding you applications immediately; all Dev no Ops! This session will also provide the attendee with information on how to find new APIs, what to be looking for and how to use them in your next application.

Published in: Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Creator of the Mule project: first open source ESBFounder the company behind Mule and its family of productsSit firmly in the love marmite campStarted my career working in banks, telco and insuranceI have always been a “plumber” 14 years experience hooking stuff togetherUltimately I’m a geek that likes to tinker with softwareHuge lego fan, obsessed as a kid. Family guy cracks me up – my wife does notget either one
  • Center of gravity shifting to the cloudRise of the composite appLess visibility and controlRapid innovation means middleware must adapt and support change
  • Building it themselves
  • Building it themselves
  • Building it themselves
  • Building it themselves
  • Building it themselves
  • ComplexityCoolnessAccessibilityCapabilitiesDisruptiveness
  • Not all APIs are created EqualWorking with different APIs is a PITA
  • NewsFeedStream note that I took the streaming stuff out for the Mule Summit since it one more concept that they needed to get their head around
  • From DevOps to NoOps: 10 cloud services you should be using

    1. DevOps to NoOps10 cloud services you should be using Ross Mason, MuleSoft @rossmason, @mulejockey
    2. About Me
    3. Agenda• Impact of APIs• Top 10 you should be looking at• Integrating with APIs
    4. The Impact of APIs
    5. API Proliferation Source: Programmable Web
    6. The traditional 3-tier architecture Client HTML Presentation Tier App Server Middle Tier Database Data Tier 6
    7. …is being decomposedPresentation Tier Presentation Tier Client JSON / XML JSON / XML Middle Tier Server Data database Data Tier 7
    8. …is being decomposedPresentation Tier Presentation Tier 3rd party Apps Client JSON / XML JSON / XML JSON / XML Middle Tier Server Data database Data Tier 8
    9. …is being decomposedPresentation Tier Presentation Tier 3rd party Apps Client JSON / XML JSON / XML JSON / XML Middle Tier Server API API API API API SaaS, Infrastructure Services, Data database API Social Media APIs API Data Tier API API API API API 9
    10. Platform ShiftTraditional Application Environments Application Web/App Server Database Operating System
    11. Platform ShiftNew Application Environments Application Application Web/App Server PaaS Database IaaS Operating System
    12. Technology ShiftTraditional Application Environments Application Application UI Security Database Business Logic Web Server Operating System Data
    13. Technology ShiftNewer Application Environments Application Application Security UI API Database Business Logic Web Server Operating System Data Integration
    14. Technology ShiftApplication DecompositionApplication Security UI API Business Logic Data Integration
    15. Top 10 APIsAPI Description Category MashupsGoogle Maps Mapping service Mapping 2278Twitter Microblogging Social 622YouTube Video sharing and search Video 585Flickr Photo sharing Photo 583Amazon eCommerce Online retailer Shopping 396Facebook Social networking Social 301Twilio Telephony service Telephony 290eBay Online auction marketplace Shopping Online radio service Music 201Google Search Search services Search 175 Source:, Sept 2011
    16. Top 10 Infrastructure APIs
    17. 10.• MySQL Database as a Service• Direct replacement for MySQL• Alternatives: Amazon RDS, Rackspace, Heroku• API: REST or SOAP for provisioning and controlling the DB instance• So What? – Fully managed, auto-scale, HA – Management tools built-in – API makes the service scriptable
    18. 9. S3• File System as a Service• Simple API for storing large and small files• Alternatives: RS Cloud Files, CloudLayer Storage• API: REST, SOAP or BitTorrent• So What? – Many Apps need file storage – Unlimited data – Leverage the Amazon global network, CDN support
    19. 8.• Logging as a Service• Manages logs, enables easy search and navigation• Alternatives: Splunk• API: REST, Syslog for data collection• So What? – Easy to set up, centralized view of App logs – No more ssh-ing to different boxes and tailing logs – Analytics as standard
    20. 7.• Email as a Service• Replace email infrastructure, its like normal email but way better• Alternatives: Postmark• API: REST, SMTP• So What? – Set up in minutes no need to run an email server – bulk, delivery management, analytics – Web Hooks Event API
    21. 6.• MongoDB as a Service• Create a MongoDB in seconds, continue writing your application• Alternatives: Couch One• API: MongoDB client API• So What? – Fully managed, auto-scale, HA – Management tools built-in – Code compatible with MongoDB
    22. 5. Airbrake• Error Management as a Service• collects errors generated by other applications, and aggregates the results for review.• Alternatives: ?• API: REST• So What? – Interesting approach to error management, no need to hit the logs – See errors in real-time, track and fix
    23. 4.• Application Security as a Service• User account management, authentication, and access control in your application• Currently in private Beta• API: REST• So What? – Every app needs user security, avoid rolling the same code over and over
    24. 3.• Publish / Subscribe Messaging as a Service• Real-time, global messaging for cloud and mobile apps• Alternatives: Pusher, Amazon SNS• API: REST• So What? – Amazingly quick; as about real-time as the web gets – Asynchronous, streaming API – Cheap even for millions of messages
    25. 2.• File Sharing as a Service• Share files between all your devices and friends/co- workers• Alternatives:, SpiderOak, Wuala, etc• So What? – Great for content delivery, service handles all synchronization issues – Good way to integrate mobile with desktop and web – (Almost) everyone has it
    26. 1.• Telephony as a Service• Build text/sms and voice apps really easily• Alternatives: Tropo• So What? – This stuff was hard before Twilio came along – Integrate text/sms into your apps for alerting, udating, user confirmation, etc – Easy to create voice access to data in an app (i.e. account balance)
    27. The API Challenge
    28. All APIs are not equal• Hard to work with different APIs – Different approaches – Different security schemes – Different data formats – Different ‘interpretations’ of REST• Lots of custom code in your app
    29. iPaaS: Don’t clutter your appYour Killer App Integration Layer Cool Stuff integration PaaS
    30. Benefits• Configuration approach to APIs• Handled for you: – Security (OAuth, SAML, Basic) – Session Management – Streaming – HTTP Callbacks• Consume and invoke multiple services• Retries, Error handling• Decouple, keep your application code clean
    31. Quick Demo• Listen to Salesforce Chatter API for messages• ‘#now’ tag in Chatter messages get filtered• Calls Twilio API to send an SMS to the user’s phone 31
    32. The Flow<twilio:config name="twilio-default" accountSid=”xxxxxxx" authToken=”xxxxxx"/><sfdc:config name="salesforce-default" username=”xxxxx" password=”xxxxx"/><flow name="sendSmsNotifications"> <sfdc:subscribe-topic config-ref="salesforce-default” topic="/SMSNotifications"/> <logger level="INFO" message="#[payload]"/> <regex-filter pattern="#now"/> <twilio:send-sms-message config-ref="twilio-default" accountSid=”xxxxxxx" from=”+14086457888" to="#[map-payload:To__c]" body="#[map-payload:Text__c]"/></flow> 32
    33. Summary• APIs are becoming part of our application architecture• All APIs are different making them hard to consume• Coding directly to APIs clutters the application and creates a dependency (tight-coupling)• iPaaS can do the integration heavy lifting, decouple your app from the APIs it consumes
    34. Questions, Ideas, Comments?• Mule iON free account :• Twitter: @rossmason, @mulejockey• Blog:• Company: (we’re hiring!)