The motto of Bluemix seems to be that developers should be able to use whatever tools they want to build their dream application. Bluemix does not intend to lock developers into a specific tool set. Vendor lock-in is an easy trap to fall into and one that can deter users from certain platforms. However, in terms of deployment, Bluemix takes measures to ensure that developers are comfortable with the way they deploy their applications.
In short, there are three main ways to deploy an application on Bluemix as summarized below:
1. Command line
Bluemix leverages the Cloud Foundry command line interface to help developers push their application through the standard command line. This interface is incredibly easy to download – you can get started with using it in a matter of seconds. It allows you to scale your applications with a simple plug-in to use.
The commands start with a “cf”, standing for the open source Cloud Foundry. In order to push an application onto Bluemix, the entire command would consist of ‘cf push my_application_name”. The source code can be found here and as a developer, it is always nice to know that the code is being pushed on a daily basis.
In essence, the command line is extremely easy to use, familiar to most developers, and allows you to see logs while pushing applications.
2. Eclipse plug-in
Next, Bluemix allows developers to use Eclipse to push their applications. IBM has developed a plug-in that makes it incredibly easy to push their applications. In order to download the plug-in, you can check out the Eclipse marketplace. Note that this is intended for Eclipse Luna for Java EE Developers.
The key takeaway here is that Bluemix caters to Eclipse developers. You can push your application to the cloud without having to leave your development environment. The process for sending over your application to your customers has never been easier. For more information, please see this fantastic tutorial on getting an application started with the Eclipse plugin.
3. ibm devops services
Lastly, IBM DevOps Services can be used for the developers that want to utilize a web IDE to write their code, store their code, track their code, and push their code. The pro of IBM DevOps Services is that there is a ton of features and functionality. The con of IBM DevOps Services is that there is a ton of features and functionality. The learning curve can be steep to understand this product, but it will be well worth it in the long run.
IBM DevOps is directly built in and integrated into Bluemix. There is even a button to “Add Git” in Bluemix which creates a code repository for you in IBM DevOps. Or you can link your source code to a GitHub repository for ease of use. The features of this product is too vast to discuss here and is beyond the scope of this post, but they are summarized below.
- Create, build, test, and deploy applications on Bluemix with IBM DevOps Services
- Agile tracking and planning
- Automated builds, test execution, and delivery pipeline deployments
In conclusion, Bluemix is a fantastic platform. The true power of Bluemix comes from the flexibility that it provides developers in terms of allowing them to use the tools of their choice. So, whether you want to use the command line interface, Eclipse, or a web IDE, you can push your applications on Bluemix with any or all of these choices. Happy development.