Over a million developers have joined DZone.

Best Practices for a Private PaaS Implementation

· Cloud Zone

Build fast, scale big with MongoDB Atlas, a hosted service for the leading NoSQL database on AWS. Try it now! Brought to you in partnership with MongoDB.

Stackato Private PaaS Architecture DiagramUsually customers have come to us after trying to build their own private PaaS from scratch or from using a variety of open source components, However, for a wide variety of reasons, it doesn’t quite materialize the way they originally hoped. As a result, the focus for companies shift from developing their own PaaS to purchasing one and integrating it into their organization.

When looking to incorporate any enterprise system, it requires the proper planning and resources in order to make it successful. Companies need to consider the organizational, process and technical layers involved. This includes establishing a program strategy, developing clear business objectives and assessing their application portfolio. One of the key considerations in the implementation of a private PaaS is having an understanding of how the architecture and workflow will impact the existing infrastructure.

Architectural Considerations for your Private PaaS Implementation

When implementing a private PaaS, you need to design an architecture for each environment (development, testing, staging, and production) that is right for your workflow and applications. There are a few key considerations when planning how to distribute roles among the VMs in your Stackato cluster when doing this:

  • Distributing load: whether or not there are sufficient routers, and application instances to support the expected and unexpected load
  • Minimizing single points of failure: building active-active redundancy in the system architecture
  • Persistent or Block Storage: back the relevant roles with block storage to leverage storage technologies and solutions
  • CPU and memory utilization: ensure that the DEAs have sufficient resources to take on the deployed application instances

You need to know your applications well in order to plan for an architecture that suits the type of applications you intend to deploy. While your individual setup will vary depending on the number of clusters your enterprise requires, getting the architecture right is an important step in a successful implementation of private PaaS.

For more information about implementing a private PaaS in your enterprise, download the white paper “Best Practices for a Private PaaS Implementation” written by ActiveState and Cloud Technology Partners.  

Now it's easier than ever to get started with MongoDB, the database that allows startups and enterprises alike to rapidly build planet-scale apps. Introducing MongoDB Atlas, the official hosted service for the database on AWS. Try it now! Brought to you in partnership with MongoDB.


Published at DZone with permission of Kathy Thomas, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

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

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

{{ parent.tldr }}

{{ parent.urlSource.name }}