Service Foundry
summary
Argues for a “service boundary” that lets operators CF push services (databases, Redis, RabbitMQ) with clear claims: change data services (Cassandra clustering, RabbitMQ automation) and change the platform to support Diego + persistent disk so services can be run inside Cloud Foundry. Explains concrete blockers — CAP tradeoffs, BOSH slowness, unclear scaling (instances vs disk vs IOPS), automation gaps — lists tools to integrate (Flocker, Calico, Weave, Consul/Zookeeper, Terraform/Brooklyn) and admits the system is not yet built and seeks collaborators.
AI-written summary · about