I've read through this but couldn't find any documentation as far as APIs (or the SPI that exists now).

> 3. What about HA for the database tier, is there support for database
> failover?

That is something we're working on, but not ready for use yet.

I'm interested in helping with this, how can I get involved? Could you tell me more about the proposed architecture? Is there a PEP out there somewhere?

> For the data tier, I'm looking to do some serious scaling (150GB Solr
> Database). Are there plans to support different gear sizes for
> different tiers of the application? The web fronts for an
> application don't need 150GB of disk quota or 16GB of ram each. In
> my case they need far, far less than this. For example, I'd like to
> have an application that uses one size of gears for say the tomcat
> gears and a different size for the mongodb gears.
>
>
> Also, are there any plans for scaling of databases (i.e. adding read
> replicas)?

Setting different gear sizes within the same application is ready in Origin master, I believe - look for that capability to roll out shortly.

Fantastic. I'll be on the lookout.

I doubt OpenShift is going to be a good place to locate large, scalable, HA databases for a while yet. For your project it would probably be best to handle the database separately and point to the external DB(s) with environment variable(s).

I'm also looking at openstack trove, but as I understand it trove needs some engineering to handle nosql databases. I'm wondering if that engineering time would be better spent put into openshift.