Recently, I wrote a hybrid Bluemix app which only utilized one of the provided runtimes (Python, node.js, Java, ...). The data for the app was hosted on-premise, outside the Bluemix cloud environment. As I wanted to keep my app as generic as possible, I searched for a way of how to link Bluemix app and the on-premise database. Apps sometimes store configuration data as constants in the code. However, this is a violation of the Twelve-Factor App principles. The configurations may vary across different app deployments, the code does not. So I looked into how to put the configuration principle into practice for my Bluemix app.
One of the great things about a cloud data service is that you don’t have to worry about upgrading versions of the software, or applying multiple fix packs. This is done for you automatically and on the fly—without any action on your part. This is a major benefit of the cloud and one of the many reasons why there is a rush to ‘as-a-service’ solutions.
This post compiles five of the most helpful resources I have come across. Why five? Well, I want to keep it relatively pointed and easy (for both of us)! Bluemix and Cloudant are continually evolving so inherently resources and articles become dated and new timely and exciting materials will come out for you to enjoy. I plan to update this post as new, more pertinent resources become available. I’ll archive some of the trusty standbys as new content comes available.