Re: Scaling Services

Alberto A. Flores

My 2 cents:

Your database, while it's deployed in CF, it's based on MySQL. Depending on
the configuration (YML file) you used for that release, scaling that
database is strictly based on whatever MySQL can provide. It's not CF, but
it's BOSH and the Software (in this case MySQL) that enables the "scaling"
of the software. All CF provides is the ability to connect apps to this db
service using the "service broker" model. In other words, CF does not scale
your service, but the BOSH release (e.g. cf-mysql-release) may be
configured to scale using features available in both BOSH and the software
(e.g. MySQL).

With regards to where to save "profile pictures", I've learned that the
right answer is always driven by the "access pattern" of the data. The S3
solution may work, but if you only archiving you can certainly wonder if
it's cost effective to do it that way. The docs you suggest refers to
writing data to disk as an anti-pattern. In general, CF allows to implement
patterns described in the "12 Factor App"

With regards to scaling, there are others factors you can consider. Perhaps
putting an "in-memory" store as a service to your app that can hold certain
type of data. I think there's more than one way to skin the cat.

Alberto Flores

On Tue, Jun 2, 2015 at 5:12 PM, Flávio Henrique Schuindt da Silva <
flavio.schuindt(a)> wrote:

Hi, guys.

I'm a beginner in using CF and I successfully deployed cf-mysql-release
[1] and now I can write, read, etc from the database as a service bound in
my application.

Now, I have some questions and it would be really great if someone could
help me.

a) Ok, I have a database that works and its great. Imagine a scenario that
a lot of clients are acessing my app and now I have to scale. How CF scale
the service? I mean there must be some way to give more nodes on the maria
db cluster provided by [1], right?

b) If I need to save profile pictures to a user table. What should I do?
Save it as blob in the database since write data to disk is not recommended
by cf docs because apps are isolated each other in the DEA.

Thank you very much for your patient and time.

[1] -

cf-dev mailing list

Join to automatically receive all group messages.