Re: Database implementation as a cloud foundry app
Daniel Mikusa
On Sun, Mar 20, 2016 at 11:36 PM, Sundarajan Srinivasan <
sundarajan.s(a)gmail.com> wrote: Dear People,If you don't want to use a service that you acquire through a service broker & CF's marketplace, you can host your database somewhere else. There's nothing that says your database and app must live in CF. The easiest way to use an external service is to create a user provided service. This contains the information to your service and works just like a service you acquire through a service broker.
Yes. If this is the case they how come the scale in and scale out happens toAt the moment, scaling the database is up to the database provider (i.e. whomever runs the service & service broker). The service broker is just an interface so that CF knows how to provision services automatically. Everything else (running, managing, scaling) the service happens outside and is the responsibility of the service provider, not CF. Not at the moment. I believe there are some recent threads on this list about this topic. You're right the default max disk size (i.e. cf push -k) is 2GB. The local file system is also ephemeral, meaning you should never write anything important there because it will go away after the app is restarted / restaged. If you're an administrator, you can change the limit. https://github.com/cloudfoundry/capi-release/blob/master/jobs/cloud_controller_ng/spec#L432-L437 Dan |
|