Want to integrate MongoDB into your Cloud Foundry App? Learn exactly how to do that with Bluemix Developer Advocate Jake Peyser! Follow him @Jakepeyser.
3. 3
So what is Bluemix?
*Bluemix Local coming Summer 2015
Customer Managed
Service Provider Managed
Infrastructure
as a Service
Code
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
Code
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
Platform
Built on open
technologies:
Bluemix is an open-standards, cloud-based platform
for building, running, and managing applications.
4. How does Bluemix work?
Bluemix is underlined by three key open compute technologies: Cloud Foundry, Docker,
and OpenStack. It extends each of these with a growing number of services, robust
DevOps tooling, integration capabilities, and a seamless developer experience.
4
Flexible Compute Options to Run Apps / Services
Instant Runtimes Containers Virtual Machines
Platform Deployment Options that Meet Your Workload Requirements
Bluemix
Public
Bluemix
Dedicated
Bluemix
Local*
DevOps
Tooling Your Own Hosted Apps / Services
Integration
and API Mgmt
Powered by IBM SoftLayer In Your Data Center
+ + +
+ +
Catalog of Services that Extend Apps’ Functionality
Web Data Mobile AnalyticsCognitive IoT Security Yours
+
*Bluemix Local coming Summer 2015
+ Always focused on what’s next
5. Where does Cloud Foundry fit in?
Cloud Foundry is the underlying PaaS behind Bluemix. It enables teams to practice
continuous delivery by making it easier to deploy, run, and manage apps.
5
Flexible Compute Options to Run Apps / Services
Instant Runtimes Containers Virtual Machines
Platform Deployment Options that Meet Your Workload Requirements
Bluemix
Public
Bluemix
Dedicated
Bluemix
Local*
DevOps
Tooling Your Own Hosted Apps / Services
Integration
and API Mgmt
Powered by IBM SoftLayer In Your Data Center
+ + +
+ +
Catalog of Services that Extend Apps’ Functionality
Web Data Mobile AnalyticsCognitive IoT Security Yours
+
*Bluemix Local coming Summer 2015
6. Cloud Foundry
6
The industry-leading open PaaS
• Clouds - Public, Private, Open Source
Choice
• Runtimes - node.js, spring, rails, etc.
• Services - MongoDB, MySQL, PostgresSQL, etc.
• Decreased time needed to prototype
Benefits of PaaS
• Deploy new code more rapidly
• Services can be self-assembled to create integrated apps
• Scale applications more elastically
• Removes worries of OS and middleware patches
• Development methodologies must adapt to tech
Disadvantages of PaaS
• Requires dev awareness of web app limitations
and best practices
• Control over underlying infrastructure is limited
7. The Cloud Foundry Foundation
7
Mission statement is to establish and sustain Cloud Foundry as the global industry
standard open PaaS technology with a thriving ecosystem
8. Cloud Foundry Architecture
8
•Platform is abstracted as a set of large-
scale distributed services
•Components are dynamically discoverable
and loosely coupled
•Uses Cloud Foundry Bosh to operate the
underlying infrastructure from the IaaS
provider
•Uses a dynamic router to shape and route all
traffic and orchestrate load balancing
•Droplet Execution Agents (DEAs) are
responsible for the app lifecycle
•Health Manager monitors and maintains
application uptime
•Buildpacks detect app runtime and
compile source code into executable binaries
9. Cloud Foundry Services
9
Types of services
•Accounts for a SaaS application
•Databases on a multi-tenant server
•Plans for messaging providers
How it works
•When a user adds a service, an instance
of that particular service is provisioned
•A service broker handles communication
between CF and the service itself
•Service processes run on Service Nodes
or with external as-a-service providers
Services allow users to provision resources on demand
10. Databases on Cloud Foundry
10
Easily provision, configure, and maintain open source database instances
DBaaS
•Easily provision instances
•Datastore choice is left to the developer
•Multiple SQL and NoSQL options
•Minimal configuration required
Best Practices
•Avoid writing to the local file system
•Files disappear after app restart
•Instances of same app do not share LFS
•Session data should be stored in CF service
•Design as if app can be restarted, destroyed,
starts at any time