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

Production-proven Mesosphere DC/OS is now even better with GPU scheduling, pods, troubleshooting, enhanced security, and over 100+ integrated services deployed in one-click.

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.

Simply build, test, and deploy. Mesosphere DC/OS is the best way to run containers and big data anywhere offering production-proven flexibility and reliability.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

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

{{ parent.tldr }}

{{ parent.urlSource.name }}