Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Carmen Gonzalez, Elizabeth White, Jason Bloomberg

Related Topics: Open Source Cloud, Machine Learning , Agile Computing

Open Source Cloud: Blog Post

Don't Fumble the Hand-off

Avoid application configuration errors by standardization and sharing

Imagine for a moment that you’re a software developer who has been charged with adding a new feature into your company’s billing system application that allows bills to be automatically sent to customers via email. You spend weeks, possibly months, working on the new function, and then at some point you move to the unit testing phase. You set up an environment, configure the product with the new feature, and then you run tests to verify that emails with valid billing information are indeed being sent as expected. Once you’re satisfied with the unit testing, it’s time to hand it over to the testing team so they can put it through the paces.

At this point you have come to the time dreaded by just about all teams involved in the application development lifecycle: The Hand-Off.

If any of you reading this have spent time in software development, you’ve undoubtedly dealt with the hand-off that occurs when one team officially passes on new versions of an application or software package to another team. These hand-offs occur between many different teams including development to test, test to QA, and QA to production, but no matter which teams are involved the room for error during these transitions is typically quite large.

So why is this period in the application lifecycle so difficult and error-prone? Well perhaps the biggest reason for complication is that the team that is handing off the updated application must explain, document, or otherwise express the parameters within which the application is expected to work. In an application environment, this means accurately describing the application server topology, application configuration, application dependencies, and more.

If one element in the environment is not precisely and accurately described, then the behavior of the application can be radically changed. In the example above, consider that an SMTP server hostname is part of the application configuration. In your unit testing environment you’ve obviously configured it correctly because you’ve already verified emails are being correctly sent. However, when you hand over the application to the test team, what happens if they make a simple typo when configuring the hostname? How long will it take you or another debugger to track down the reason why all of a sudden emails are no longer being sent?


That is certainly a simplified example, but the point is as developers, testers, and administrators, how much of our time is spent tracking down “bugs” that are really caused by inconsistent configuration? I know I spent quite a bit of time tracking down these types of bugs while I was in development, and I’m pretty sure that if you are in software development that you have too.

So then, if the discussion above is about the problem, what’s the answer? Obviously the answer is that companies need solutions that allow them to internally standardize, preserve, and share application environments and application configurations. If you take a look across many different cloud solutions, this is a problem that many of them attempt to address in some form or fashion. This can be done by allowing the creation of custom virtual images, custom application stacks based on virtual images or simply by allowing sharing and collaboration of application configuration files.

For us in IBM, we’ve tackled this problem by allowing customers to build, deploy, and share patterns with the WebSphere CloudBurst Appliance. Patterns are complete representations of application environments that include the application server topology, configuration, and even the application. These patterns can be built, improved and hardened over time, and shared across an organization. Members of different teams can use and deploy the same patterns, thus ensuring that the resulting application environment is consistent across the different contexts of an organization. In short, patterns provide consistency and repeatability with respect to a company’s interactions with their application environments.

If you want to read more about WebSphere CloudBurst patterns and their role in building up customized application environments, take a look here or watch some of our demonstrations here. Regardless of whether or not WebSphere CloudBurst is right for your particular needs, I’d encourage you to look for solutions that provide capabilities to standardize on and share application environments across your organization. After all, less time spent tracking down pesky configuration errors is more time spent developing and adding new value to your products.

More Stories By Dustin Amrhein

Dustin Amrhein joined IBM as a member of the development team for WebSphere Application Server. While in that position, he worked on the development of Web services infrastructure and Web services programming models. In his current role, Dustin is a technical specialist for cloud, mobile, and data grid technology in IBM's WebSphere portfolio. He blogs at http://dustinamrhein.ulitzer.com. You can follow him on Twitter at http://twitter.com/damrhein.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Microservices Articles
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, will discuss why containers should be paired with new architectural practices such as microservices ra...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin, ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...