[eBook] Dos & Don’ts For Scaling Stateful Cloud Applications With Containers

Building enterprise database and big data applications in today’s quickly changing technology landscape is a challenge, to say the least. While DevOps has promised streamlined workflows, this loose methodology only solves a few of the many database application challenges we all face. While DevOps does solve for design, coding, building, and release, it doesn’t solve for many of the longer term lifecycle management issues enterprise teams face in managing exponential data inputs, application upgrades, scaling stateful cloud applications and functionality changes long-term.

Containers have been proposed as a solution for many of these woes. But, few have mastered their use at an enterprise level. In fact, the majority of containers break down at the storage layer, and enterprise IT teams are left frustrated. This has led many to believe that containers should only be used with stateless applications.

At Robin, we know that building, scaling stateful cloud applications, and managing a stateful big data or database application with containers is not just feasible, it also unlocks incredible improvements, hardware utilization, and overall application performance.

But don’t take our word for it. We recently caught up with 10 of the leading thinkers across big data, databases, containers, and DevOps areas to help us frame up a new eBook: Dos & Don’ts For Building Stateful Cloud Applications with Containers.

While some of these insights came as no surprise, others were brand new to us. Here’s a sample of what they had to say.

“Non-essential container elements should be spun off into other containers.”

Eric Vanderburg

Eric Vanderburg, Director, Information & Cyber Security, JURRINOV, LLC

“Maintaining an isolation between the container and hosts system by separating the file systems is vital.”

Dr. Craig Brown

Craig Brown, PhD, Senior Big Data Architect & Data Science Consultant, Big Data Consultant

“Keep all the tests, test tools and test meta data in a separate related container.”

Marc Hornbeek

Marc Hornbeek, Principal Consultant – Dev Ops, Trace3

“The logging strategy for containerized applications needs to be planned in advance.”

Stephen Thair

Stephen Thair, Co-Founder, DevOpsGuys

“Let the data provide the facts and guide to the optimal solution and use of containers.”

Steve Brown

Steve Brown, Director, DevOps Solutions N.A., Lenovo

Even infrastructure people can and should be excited about containers.

Stephen Foskett

Stephen Foskett, Proprietor, Foskett Services

“Follow good microservices design practices for distributed data design.”

JP Morganthal

JP Morgenthal, CTO Application Services, DXC Technology

“When dealing with stateful applications, precautions need to be taken to ensure that you are not compromising or losing data.”

Sylvain Kalache

Sylvain Kalache, Co-Founder, Holberton School

Whether you are migrating an existing enterprise application or building one from scratch, containers are just part of the puzzle. The expansion of the cloud and expectations for greater simplicity, agility, security and on-demand performance are all stacking up fast against enterprise teams. Combined, these factors are flooding IT and database teams under insane volumes of data and throwing up the scaling stateful cloud applications challenge.

If you’re ready to overcome these challenges, download our eBook today.

mm

Author Razi Sharir, Vice President Products & Marketing

More posts by Razi Sharir, Vice President Products & Marketing

Join the discussion One Comment