DevOps: Is it here to Stay?

With the Agile methodology closing on its third decade of use, one of its offshoots – DevOps – is transitioning from the latest technology buzzword to an IT industry standard. The raw numbers reveal the growing popularity of the software development framework – slash – organizational structure. A recent study noted 74 percent of businesses now make some form of DevOps investment.

Does this increase in adoption in the business world mean DevOps is finally here to stay? Will it continue to grow in demand, or is another methodology just around the corner? Leverage these insights to drive your own decisions on the right framework for your software shop.

Why are Companies moving to DevOps

A recent “State of DevOps” study, highlighted in Information Week, reported that companies with successful DevOps implementations are able to deploy code – new features and bug fixes – 30 times faster than before. Considering the competitive business environment in this era of social media, organizations choose DevOps simply to keep up with the other firms in their sector. Another notable advantage is the 50 percent lower fail rate on deployments!

Less downtime leads to higher productivity, allowing companies to set a more aggressive timeline on their projects. Improved collaboration and communication among your stuff also serves to boost employee morale, leading to higher retention and lower HR costs.

The Demand for Experienced DevOps Engineers Grows

Another key indicator of continued maturity of DevOps is the high demand for engineers experienced in the practice. The average salary for these IT professionals is now over $100,000 according to Glassdoor. The staffing website, Indeed notes the DevOps engineer is the hardest role for companies to keep filled.

Expect this trend to continue, as more companies transition to a DevOps model, and require experienced professionals to help achieve a good return on their investment. Even as more processes become automated in DevOps, the demand for talented software development, network engineers, or a mix of the two won’t be going away.

DevOps Tools – and the Cloud – also becoming more Popular

The emerging popularity of DevOps is essentially matching the increase in Cloud usage at businesses. Companies leverage Cloud-based development environments using tools like Docker and Chef to lower costs and make processes work more efficiently. The latter remains one of the reasons organizations are able to increase deployment speed by 30 times, as noted earlier.

Tech industry analysts predict Cloud investment at businesses is expected grow for at least the next decade. In most cases, these organizations will continue to leverage a DevOps model to get the most out of their Cloud implementation. It is therefore reasonable to assume DevOps will continue to cement itself as the standard when it comes to the organizational structure in the IT world.

Striving for more efficiency in a competitive business environment made companies explore DevOps in the first place and will keep it as an important tool in the arsenal of the top software development organizations in the industry. This undoubtedly means DevOps is here to stay for the foreseeable future.

When you are looking for additional insights on the software development world, keep coming back to the Betica Blog. As always, thanks for checking it out!

Add Chef to your Organization’s DevOps Kitchen

Companies looking at DevOps with the hopes of streamlining their software development process sometimes struggle with the initial implementation. Leveraging the right set of DevOps tools is an important factor in achieving success as much as any organizational or policy-based changes. One such tool – known as Chef – is especially helpful for shops taking advantage of the Cloud as part of their overall application engineering strategy.

What follows is a closer look at the features and functionality of Chef to see if it allows your team to manage server infrastructure quicker than ever before.

Open Source Server Configuration Management for the Cloud… and more

Chef’s main functionality centers on the management of Cloud-based infrastructure. It offers value to any company whether they manage ten servers or ten thousand – no matter the platform. It lets your development staff focus on ensuring their software runs properly, instead of having to deal with the drudgery of server administration tasks. While it truly shines in the Cloud, Chef also works with on-premise servers as well as a hybrid infrastructure.

A Code-based Approach to Server Management

What makes Chef unique among similar infrastructure management tools is its emphasis on using code to define and automate a collection of servers. This lets you handle automated server management in a similar fashion as your applications, with development, QA, and production environments ensuring a high level of quality. Additionally, letting your developers manage servers using code fits nicely with the overall philosophy of DevOps, where formerly segregated duties are handled in a more communal fashion.

A development kit, known as the Chef DK, includes everything required to develop and test infrastructure automation code. Test Kitchen handles the running of these tests, using InSpec as the TDD programming language. Not surprisingly, the included code analysis tool is known as the “Food Critic.”

Continuing with this kitchen metaphor, the collection of code used to automate and define a server infrastructure is known as a cookbook, and – of course – they are made up of recipes. This nomenclature definitely helps developers new to Chef better understand the functionality of each part of the system. Behind this somewhat humorous style lies a very powerful tool.

The Chef Server is the central repository for every cookbook in the system. This design allows the Server to manage any number of physical or virtual machines in your infrastructure. The Chef Client runs on each of these nodes; staying in constant communication with the Server.

An Essential Tool for DevOps

As noted earlier, Chef offers any DevOps organization the means to manage their technical infrastructure easier than before. Its code-based scheme for server management lets you leverage your development talent in a new fashion. The kitchen-based metaphor used in Chef also makes it easy to understand by both your technical and non-technical team members.

Chef, and similar tools, like Ansible which we previously covered, play an important role in any company deriving value from its investment in DevOps. Ultimately, this is a methodology requiring more than just a change in organizational structure for success. Download Chef to see if it makes sense in your shop.

Thanks for reading the Betica Blog. Keep coming back for additional insights from the software development world.

News from the World of Software Development – June 2017

Welcome to the June edition of the Betica Blog software development news digest. We hope this month’s stories provide a measure of insight and inspiration to compliment your daily work routine. If you are interested in checking out last month’s stories, including the increased use of Agile at government agencies and Microsoft embracing Git, simply click on the following link.

The Forecast for Software Development is Cloudy

Companies continue to leverage Cloud-based services to make their software development processes more efficient. This trend was reported on earlier this month at the blog for the document management software company, Formtek, as well as other sources.

 This migration to the Cloud is a natural outgrowth of organizations increasingly adopting Agile, DevOps, and other modern development frameworks with the hopes of achieving continuous integration or to simply deliver software faster. Some of these Cloud-based services include containers and virtualized server environments, as well as QA and database services.

Formtek explains that because many development companies are actually writing software to be run in the Cloud, it makes using Cloud-based tools a natural fit. This fact is highlighted in their three top reasons why software engineering becomes more efficient in the Cloud. In short, developers are already using the Cloud in their daily work; they want to use new tools which are largely Cloud-based, and DevOps and Continuous Delivery largely depend on Cloud-based tools.

The future of software development is quite cloudy, indeed.

Volvo and NVIDIA working on Driverless Car Technology

While NVIDIA is primarily known as a developer of graphics processor chip technology, the company is working with Volvo and two other companies on a driverless car system. News about this futuristic consortium first appeared this week in Forbes.

The heart of this new technology is NVIDIA’s Drive PX automotive computing platform. The company’s graphics processing background comes into play with Drive PX’s auto-pilot functionality, which is able to read real-time information from 12 HD cameras, processing 1.3 gigapixels of graphics data per second. The system uses dual high-powered Tegra X1 chips, capable of recording two 4K streams at a refresh rate of 30Hz.

Software routines using AI and deep learning are able to make intelligent decisions based on all that graphical data. This facilitates object detection while allowing for the automated control of the vehicle. The first driverless cars from the Volvo/NVIDIA group are expected to hit the marketplace by the end of 2021.

Crowdtesting grows in Popularity

As software companies hope to improve their QA processes, a new form of quality assurance – crowdtesting – is growing in relevance. Applause, a company involved in the practice, recently described how it works on its ARC website.

At its essence, crowdtesting uses the targeted audience demographic of an app as part of its testing team. The hope is to have the QA process mimic the real world environment of a website or mobile app as closely as possible. Applause currently has over 300,000 testers available across the world, so it is able to match a group of testers to most applications.

It will be interesting to see if crowdtesting becomes part of the QA mainstream in the next few years.

Stay tuned to the Betica Blog for additional news and insights from the constantly evolving world of software development and QA. As always, thanks for reading!