A few comments about some future direction of OpenShift, and how it might affect the business cases you mention. I'm speaking less specifically about OpenShift Online than about OpenShift as a project below.
On Jan 2, 2015, at 2:16 AM, Andrew Galdes <andrew galdes agix com au> wrote:
In this specific case, our general story is that is why OpenShift is an open source project with an enterprise support focused story - to allow these users to deploy their own OpenShift. But even those organizations can find benefits in having aspects of their web dev and development flows running on the Online version. For greenfield apps, this is always a much easier story, but there are many existing apps with components that are suitable to the OpenShift model as it exists today. This "hybrid" model we expect to grow as organizations become less attached to physical infrastructure (internal or external) and focus on application definition and composability.
Databases definitely are a linchpin of many "growth scenarios" where someone is transitioning from idea to production and then growing past that. Our goal has always been to provide a reasonable foundation for that flow (starting with simple, push button db deployments) but as you note in some cases the need to tune and manage that DB works at odds with the current OpenShift story. Today, that story might be DBs managed externally (by an in house team or an IaaS service), but a degree of planning is involved in how you transition across those scale boundaries. Going forward, I see two improvements to that story:
- newer databases (nosql and sql alike) are increasingly self tuning and have lower operational overhead to scale, which reduces the cost to prepackage and deploy them on top of infrastructure (as VMs, or as OpenShift cartridges) in a scalable way
- that OpenShift is moving towards making database like components easier to deploy and manage themselves by leveraging paas and IaaS ideas (offering finer grained controls on those components). A large part of the OpenShift 3 architecture is around the idea of finding a lower level of common building block for all networked software, not just web dev style solutions. E.g. Several blog posts recently about large companies using massive Cassandra clusters inside Docker containers in production - that story would directly carry over to OpenShift in our next gen architecture, so a blurring of the lines between web dev and other types of networked apps.
So over the longer term I see a future where there is increasing ability to deploy databases as needed and scale them on OpenShift, with deeper visibility into the underlying tuning to make vertical scale databases work efficiently, while being able to centralize operational and monitoring workflows across many different types of components.