To properly deploy an application in a cloud environment and ensure maximum responsiveness, your app needs to be deployed in a certain (and easy) way that maximizes the chance of an instance always being ready to respond to a user request. This article will explain how to deploy your Cloud Foundry applications in the IBM Cloud such that you reach your target application availability.
If you're like many developers who are deploying applications to Cloud Foundry, you probably don't think about networking too often. After all, as a PaaS, Cloud Foundry takes care of all the routing and connectivity for you. There is one feature, however, you might consider before writing your next app: container-to-container networking.
Mobile apps tend to exhibit high variability; hence, developers often find it difficult to size the mobile backend for their app. This post offers a quick back-of-the-envelope sizing calculation so developers can set up an enterprise-grade backend for their app.
We are deprecating the Application Management feature, and it will eventually be removed. With the removal of Application Management, your Node.js droplet will be smaller so your push times to the cloud could become shorter.
With Cloud Foundry Enterprise Environment (CFEE), you can instantiate multiple, isolated, enterprise-grade Cloud Foundry platforms on demand. Instances of the CFEE service run within your own account in IBM Cloud.
Do you need to select the right technologies to build the next productivity app in your application backlog? Get your hands dirty with those technologies before you start your build. Download the CloudCoins wellness app and use the git repo to tinker under the hood.