Date post: | 17-Dec-2014 |
Category: |
Technology |
Upload: | platform-cf |
View: | 1,715 times |
Download: | 2 times |
1
Service Distribution to Any Cloud
Mark Geene @mgeeneVineet Joshi @cloudyvineet
2
A cloud services development and integration company that leverages pre-built Elements to accelerate the development of cloud applications on Cloud Foundry
About Cloud Elements
3
Elements reduce the cost to integrate, monitor and maintain leading cloud services:- Messaging – SendGrid, Twilio- Documents – Box, Dropbox, Google Drive- Payments – Authorize.net, Paypal, Amazon- SSO – Facebook, GitHub, Google- Social – Facebook, Instagram, Twitter, Flickr- CRM – Salesforce.com, SugarCRM
Our Elements
4
Documents Hub Example
Element Hubs Provide One-to-Many Integrations
Documents Hub
K
Any File API/Service
Your App
5
Need to deploy our technology anywhere. Our client’s private, hybrid and public clouds
Independence from technology dependencies such as different runtime containers and versions
Too much time spent managing deployments due to lack of standardization
Our Deployment Challenges
6
Design to the PaaS v/s the IaaS Adhere to a strict separation
between layers Select a portable PaaS to facilitate
frictionless distribution to different IaaS endpoints
Anchor services to a runtime available in the PaaS
Deploy as a Custom Service in Cloud Foundry
Our Approach
7
1. Design your service using a SOA & RESTful Integration Model
2. Pick from Runtimes and Data Services supported out of the box by Cloud Foundry- Using an non-standard runtime will make your application
less portable to any infrastructure- Using non-standard databases will mean you have to
bundle the DB with your component
Cloud Foundry Custom Service Best Practices
8
3. Don’t Use IaaS services/APIs directly- When an IaaS service or API needs to be used,
reference it via a service in the PaaS- Increase your portability to any infrastructure
4. Make your Service Stateless- Allow Cloud Foundry to balance the load across
instances without worrying about state transfer- Allow Cloud Foundry to add/remove instances as
required
Cloud Foundry Custom Service Best Practices
9
5. Leverage the built-in Cloud Foundry Security v/s using a non-standard, custom implementation in your service- Cloud Foundry’s UAA provides OAuth 2.0 security, which
is becoming the de-facto standard for single-sign on and ID management
6. Manage releases and deployment via BOSH- We started with vcap, but migrated to BOSH- Allows you to use a standard deployment model- Reduce your DevOps cost by leveraging BOSH
Cloud Foundry Custom Service Best Practices
10
7. Leverage Cloud Foundry Custom Services to facilitate Self-Service - Distribute your Custom Service via a Marketplace- Provide self-service provisioning APIs- Leverage Cloud Foundry to allow your customers to
manage scale- Leverage Cloud Foundry for service monitoring
Cloud Foundry Custom Service Best Practices
11
30% Savings across development budget Deploy in hours to new IaaS environments
and private clouds v/s weeks Significant improvement in monitoring,
maintenance and support Expect increased savings with new Custom
Services approach in 2.0
Results
12
Cloud Elementswww.cloud-elements.com
Mark Geene @mgeeneVineet Joshi @cloudyvineet
13