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

DevOps to NoOps10 cloud services you should be using Ross Mason, MuleSoft @rossmason, @mulejockey

About Me

Agenda• Impact of APIs• Top 10 you should be looking at• Integrating with APIs

The Impact of APIs

API Proliferation Source: Programmable Web

The traditional 3-tier architecture Client HTML Presentation Tier App Server Middle Tier Database Data Tier 6

…is being decomposedPresentation Tier Presentation Tier Client JSON / XML JSON / XML Middle Tier Server Data database Data Tier 7

…is being decomposedPresentation Tier Presentation Tier 3rd party Apps Client JSON / XML JSON / XML JSON / XML Middle Tier Server Data database Data Tier 8

…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

Platform ShiftTraditional Application Environments Application Web/App Server Database Operating System

Platform ShiftNew Application Environments Application Application Web/App Server PaaS Database IaaS Operating System

Technology ShiftTraditional Application Environments Application Application UI Security Database Business Logic Web Server Operating System Data

Technology ShiftNewer Application Environments Application Application Security UI API Database Business Logic Web Server Operating System Data Integration

Technology ShiftApplication DecompositionApplication Security UI API Business Logic Data Integration

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 213Last.fm Online radio service Music 201Google Search Search services Search 175 Source: ProgrammableWeb.com, Sept 2011

Top 10 Infrastructure APIs

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

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

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

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

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

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

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

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

2.• File Sharing as a Service• Share files between all your devices and friends/co- workers• Alternatives: Box.net, 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

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)

The API Challenge

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

iPaaS: Don’t clutter your appYour Killer App Integration Layer Cool Stuff integration PaaS

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

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

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

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

Questions, Ideas, Comments?• Mule iON free account : http://muleion.com• Twitter: @rossmason, @mulejockey• Blog: http://blogs.mulesoft.org• Company: http://mulesoft.com (we’re hiring!)

http://blogs.mulesoft.org	1893
http://blog.airbrake.io	1587
http://blog.nosqlfan.com	1207
http://www.lumile.com.ar	454
http://www.aninki.net	144
http://a0.twimg.com	82
http://paper.li	71
http://feed.feedsky.com	40
http://aninki.net	34
http://www.kuqin.com	29
http://moodle.lasell.edu	23
http://people.ntis.vn	17
http://reader.youdao.com	16
http://us-w1.rockmelt.com	10
http://www.linkedin.com	8
http://translate.googleusercontent.com	7
http://feeds.feedburner.com	7
http://pinterest.com	6
http://www.zhuaxia.com	5
http://www.onlydoo.com	5
http://zhuaxia.com	5
https://twitter.com	3
http://cache.baidu.com	2
http://localhost	2
http://webcache.googleusercontent.com	2
https://blog.airbrake.io	2
http://trunk.ly	2
https://si0.twimg.com	1
http://stage.blogs.mulesoft.org	1
https://twimg0-a.akamaihd.net	1
http://www.aninki.net.nyud.net	1
http://www.twylah.com	1
http://zootool.com	1
http://bitly.com	1
http://tweetedtimes.com	1

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

by Ross Mason

Accessibility

Categories

Upload Details

Usage Rights

35 Embeds 5,671

Statistics