Cloud Zone is brought to you in partnership with:

Mitch Pronschinske is a Senior Content Analyst at DZone. That means he writes and searches for the finest developer content in the land so that you don't have to. He often eats peanut butter and bananas, likes to make his own ringtones, enjoys card and board games, and is married to an underwear model. Mitch is a DZone Zone Leader and has posted 2576 posts at DZone. You can read more from them at their website. View Full User Profile

OpenShift and the Argument for Cartridges

01.02.2014
| 10205 views |
  • submit to reddit

We've seen how Heroku uses Buildpacks, while OpenShift and WSO2 use Cartridges for cloud app portability.  I wanted to look back on another informative post from the OpenShift blog that lays out the capabilities of cartridges.

OpenShift cartridges have an amazing amount of functionality but there are two capabilities that are my favorite:
   •   Providing a first class way to interact with each other, even across multiple machines
   •   Giving the cartridges the ability to influence their deployment topology (i.e. can they run embedded with other cartridges or do they scale differently)

Matt Hicks


Cartridges are extremely convenient because they handle the database drivers for you.  They also wire together other components and implement auto-scaling and other functionality.