Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

OpenShift and the Argument for Cartridges

DZone's Guide to

OpenShift and the Argument for Cartridges

· Cloud Zone ·
Free Resource

Discover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.

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.

Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}