A lot of companies and startups view DevOps as an option for the future. At Zipline Labs, however, we took an unconventional approach to DevOps. We’ve leveraged Rackspace DevOps Automation Service from our inception. We know that a company without a clear vision is a company without a future; and we see our technology as the loudest voice of our vision. Your technology can’t speak on a second-rate platform. We didn’t want to wait and then have to migrate all of our previous work, including any mistakes we made, to a new platform. Instead, we chose to speed development and deployments across our dev, demo, staging and production environments.
Appboy makes a marketing automation platform for mobile apps and it works with some of the largest brands in app stores, such as Shape Magazine, Urban Outfitters and many more. The problem Appboy solves for its customers is app abandonment, or app engagement – keeping users engaged and coming back to apps.
Among the presentations this week at Rackspace::Solve New York, one clear theme emerged: the power of collaboration. More than 300 attendees, including business leaders and developers from dozens of companies, spent a day in lower Manhattan sharing strategies for solving some of the toughest challenges in IT and technology.
The globe was gripped with World Cup fever this past summer. But more impressive to me was the monumental shift in the talent and performance of the US National Team. Since we hosted the World Cup in 1994, our team has matured from a ragtag group to one that can compete against top talent. There are three main drivers for this change: an inspiring leader, players in the right network and performance measurement.
Last year, Rackspace noticed a shift in the market – a growing demand from customers for the ability to continuously deploy and efficiently expand their applications to keep up with their fast-growing business. In December 2013, we answered this call by launching the DevOps Automation Service, the industry’s first “DevOps-as-a-Service” offering.
Teamwork may seem like a given in many tech companies. After all, one department relies on another to build or deploy the software being delivered. Yet when strict boundaries exist between departments, such as those dividing Development and Operations, this teamwork is more like handing off a baton in a relay than legitimate collaboration. Any effort to become more agile will be difficult, if not impossible, when those boundaries remain in place.
One of the hot debates in the DevOps community right now what exactly DevOps is and whether it even needs a definition. Community member and vendor, ScriptRock, elegantly summarized it here; Skelton Thatcher built on that here; and DevOpsGuys’ Stephen Thair continued the conversation here.
Making the transition to DevOps practices requires more than just a flip of a switch. It takes stakeholder buy-in and often requires cultural and business practice transformations that impact the entire organization. DevOps isn’t a product; it’s a methodology, and adoption takes preparation and planning. Many companies are eager to get started with DevOps, but are looking for guidance on how and where to begin.