3. Agenda
About ActiveState
Drivers for [Private] PaaS
Public PaaS vs. Private PaaS
Private PaaS Deployment Considerations
Use Cases
Wrap Up
4. About ActiveState
Founded 1997
2 million developers, 97% of Fortune 1000, open source
ActiveState empowers innovation from code to cloud smarter, safer, and faster
Some customers:
6. Layers in the cloud
SaaS: Application Layer
PaaS: Management Layer
DEVELOP DEPLOY SECURE CONTROL
IaaS: Infrastructure Layer
+ OTHERS
7. Cloud Infrastructure: Public v. Private
Public IaaS Private IaaS Private
Corporate
Lots of providers
serving government, IaaS
large enterprise, SMB Powered by:
8. The state of IaaS:
Infrastructure for clouds
implemented
Public mostly
Private increasing
13. Platform as a Service (PaaS) — the capability provided to the
consumer is to deploy onto the cloud infrastructure consumer-
created or acquired applications created using programming
languages and tools supported by the provider. The consumer
does not manage or control the underlying cloud infrastructure …
but has control over the deployed applications …
14. Platform as a Service (PaaS) — the capability provided to the
consumer is to deploy onto the cloud infrastructure consumer-
created or acquired applications created using programming
languages and tools supported by the provider. The consumer
does not manage or control the underlying cloud infrastructure …
but has control over the deployed applications …
15.
16. What? PaaS
Middleware
Operating System
Programming Language
Modules
Frameworks
Databases
Web servers
Auto Config
Seamless Deployment
17. Why? PaaS
Worry Free
Middleware
Dependencies
Configurations
Deployment
Management
Coding
Less Work
18. Platform as a Service (PaaS) — the capability provided to the
consumer is to deploy onto the cloud infrastructure consumer-
created or acquired applications created using programming
languages and tools supported by the provider. The consumer
does not manage or control the underlying cloud infrastructure
… but has control over the deployed applications …
22. xx
[Public] PaaS
Large Enterprise
Government
(some) SMBs
23. Platform as a Service (PaaS) — the capability provided to the
consumer is to deploy onto the cloud infrastructure consumer-
created or acquired applications created using programming
languages and tools supported by the provider. The consumer
does not manage or control the underlying cloud infrastructure
… but has control over the deployed applications …
24. Why? [Public] xx PaaS
No Control
Public Cloud Concerns
Lack of Flexibility
New Apps, Existing Apps
Security
Privacy (Compliance)
30. Developers get freedom
Choose the right stack
Use the best tools
Config, test and deploy faster
Build more apps
31. DevOps gets control
One platform for new & legacy apps
No data silos & rogue clouds
Tighter security & compliance
Deploy to private, public, or hybrid clouds
32. PaaS 101: Public vs. Private Security
APP
APP APP
APP APP
APP
APP
APP APP APP
APP APP
Public PaaS Private PaaS
33. CIO/Finance Gets ROI
Shorter time-to-market
Better use of assets
No vendor lock-in
Lower costs
34. Private PaaS is about…
Cloud control: Bring your cloud in-house and make your
cloud your own
Knowing where your bits are: Keep your data within
your span of control
Insourcing. Insource without taxing already
overburdened IT resources
35. What private PaaS can do #1
Setup & Develop & Manage &
Scale Deploy Monitor
• Create an AUTO- • Deploy • Manage updates,
CONFIGURING NEW, migrating upgrades
private PaaS on top EXISTING • Monitor application
of private cloud or applications to the performance
IaaS in minutes cloud in 3 simple
steps
40. Private PaaS –
A mandate, not a contradiction
Bring your cloud under control:
Develop in the language and framework that’s right for you
Protect your data…on your terms
Retake your freedom:
The public cloud scales with your data. Private cloud grows with your business.
Flexible, fast deployment
Rethink your ROI:
Buy an extra server…and resell that capacity
Turn your cost center into a profit center
48. Thank you!
Learn more at activestate.com/stackato
Twitter: @activestate, #stackato
Blog: www.activestate.com/blog
Hinweis der Redaktion
No! These are oxymorons: Jumbo Shrimp. Living Dead. Stop and Go.What he meant: Private PaaS, specifically within the private cloud model, doesn’t deliver on the promise of the public cloud’s value propositions. If the whole point of cloud is to outsource your IT and realize cost efficiency, scalability, and flexibility, what’s the point of bringing your cloud and PaaS back in-house?The Point (and the secret):For the real-world enterprise, a public cloud isn’t as secure, cost-effective, or flexible as a private cloud. Period.The truth is that a public cloud scales with your data. It doesn’t necessarily grow with your business. You heard me: Private cloud trumps public when it comes to enterprise control, operations, and risk management. And if you’re crafty, you can even make a little money off it. There. Secret’s out. But now that you know that, what do you do? The answer: Insource your cloud.
From the bare iron up, there are three layers to the cloud cake: Infrastructure (IaaS), Platform (PaaS), and Software (SaaS). YOU NEED ALL OF THEM. These layers are common—and necessary—for all three types of cloud deployment.Today we’re going to talk about PaaS, the middle layer of the cake, and how it can help you regain control of your cloud and your profits. You need it for deployment and provisioning.There are two types of PaaS: Public and Private.PaaS abstracts application hosting from physical or virtualized hardware, so that the people deploying applications do not have to concern themselves with anything but the application code. Source code is pushed to the PaaS, which configures everything the application needs to run. Developers have moved to this model in droves as it saves significant time and effort that would otherwise be spent configuring the application hosting environment.
A lot of providers in private IaaSPrivate IaaS Servers are not multi tenantWhen you move to the cloud, how much do you move? The first possibility is an Infrastructure as a Service (IaaS) environment where the networking, storage, servers, and any virtualization resources are handled in the cloud by the Service Provider. It is basically the operating system in the cloud. This takes some of the core infrastructure headaches away, in theory, but leaves much of the environment from the operating system up in the hands of the Subscriber. This level of control is desirable by some, but places a lot of the responsibility in the hands of the Subscriber. Public IaaS providers like Rackspace or Amazon EC2 help companies move core IT infrastructure resources into large, shared, elastic pools of computing power. In addition to moving these to operational expenditures (rather than costly capital investments), this enables IT organizations to outsource commoditized components and focus on value-add. These are excellent goals and many of the main reasons why IaaS is being implemented broadly by companies worldwide.  Private clouds (e.g. Private IaaS) leverage server virtualization to capitalize on the same advantages offered by public clouds. However, they provide greater security, control and customization afforded by dedicated resources.  The primary differentiator then of a private cloud is that it is operated solely for a specific organization, either by the organization itself or by a third party.  Implementation behind a corporate firewall is often vital to ensure data privacy, security and control. Private clouds make good sense for large enterprises that have specific internal IT requirements that public cloud services cannot reliably fulfill, or for companies with application or security requirements that are not compatible with the shared public resource model. Leading hypervisor providers that enable the creation of a private IaaS include VMware, Citrix, Microsoft, and others.
How to leverage the infrastruture more. Been there done that.Scaling/elasticty/central control of your entire cloud
When an enterprise uses a public PaaS, it is outside of the firewall. The providers are essentially providing a one-size-fits-all solution. This may work for new apps when development is done from scratch. But the first move for most companies will be porting existing apps. Set the variables for secruity and privacy.
When an enterprise uses a public PaaS, it is outside of the firewall. The providers are essentially providing a one-size-fits-all solution. This may work for new apps when development is done from scratch. But the first move for most companies will be porting existing apps. Set the variables for secruity and privacy.
Public PaaS: Simple provisioning and app enabling platform. Apps play within a big shared multi-tenant playground. Within that platform, apps are vulnerable to other apps. Security is lowest-common denominator.Private PaaS is a secure middleware layer. Still multi-tenant, but thanks to containerization, apps are shielded from rogue apps and playground bullies. More importantly, there’s no hack-once-compromise-all reward.ANIMATED – Click to see what can happen. (Worst-case scenario!)
Private PaaS can simplify, ease, and accelerate deployment and provisioning workflow.
Private or Public:Security, privacy?New or migration of old apps or both?# of applicationsWhich applications to move to cloudLanguages usedDatabases/FrameworksDevelopersIaas/HypervisorsMonitoringControlSupport your existing development environement
Accelerate deployment, provisioningPush 40K custom legacy apps to the cloud
No! These are oxymorons: Jumbo Shrimp. Living Dead. Stop and Go.End with a bold statement on our vision
The real-world enterprise demands private cloud, and more specifically, private PaaS: Enables easy development and deployment in any language or framework Keep your data within your span of control, maintaining governance and oversight Reduce deployment times from weeks to minutes, increasing efficiency and productivityInsource your cloud and take controlYou can always burst to the public cloud as needed.Mirrored production environment reduces deployment cycle from weeks to minutesConsider reselling your cloud capacity. Worked for a certain online bookseller…
The real-world enterprise demands private cloud, and more specifically, private PaaS: Enables easy development and deployment in any language or framework Keep your data within your span of control, maintaining governance and oversight Reduce deployment times from weeks to minutes, increasing efficiency and productivityInsource your cloud and take controlYou can always burst to the public cloud as needed.Mirrored production environment reduces deployment cycle from weeks to minutesConsider reselling your cloud capacity. Worked for a certain online bookseller…