ANZ Pied Piper

In a previous post we saw the basic usage of " cf push " to bring your Python script to Pivotal Cloud Foundry and running it. The only parameter we used at the time was the application name. If for example we did: cf push pretty_app1 This meant that our app would be accessible with " http://pretty_app1.cfapps.io ". Not to be confused with the name of the actual Python script, ex: " app.py " When we run this we got an instance with a certain default characteristics, ie  1GB RAM and 1GB of disk. Given that Pivotal bills you based on the memory used by your apps, you might want to be more specific about that, specially in our "hello world" app which requires little resources. You can see the health of your app as follows. In my case we can see it only requires 17MB of RAM, so 1GB is a huge waste. Luckily the " cf " cli tool has lots of options. You can explore them by simply typing " cf --help " or to see the opt...

As we have seen in previous posts Cloud Foundry Marketplace offers a large amount of services, including a variety of databases, message queuing, etc which will address the majority of use cases. However the offerings available in the Marketplace can be customized by the provider. For example the offerings from Pivotal Cloud Foundry might differ from Cloud Foundry on Azure or on Google Cloud Platform etc. In general each cloud provider will try to differentiate by extending the platform with whatever managed service they believe is unique to them and is going to help them attract customers. For example Google offers services like Google Cloud Storage, BigQuery, BigTable or the Machine Learning APIs, etc. Whereas Microsoft Azure offers Azure Storage, Azure SQL or CosmosDB in addition to Redis, MySQL or PostgreSQL. In any case, incorporating these services into your application should be done by reading credentials and other binding information from the environment so that we a...