The (re?)emergence of Microservices was especially prominent in this week’s news. What are they good for? do they make sense for your application? should you take the plunge? and what do Microservices mean for your DevOps and Continuous Delivery efforts?
Continue reading for more on Microservices, containers, DevOps culture, and more top news from the past week. As always, stay tuned to all the news coming from@ElectricCloud on DevOps and Continuous Delivery throughout the week and retweet/favorite to get your favorite pieces featured in our weekly recap!
(Also: To learn more about Microservices and how they impact your CD Pipeline join us on the next #c9d9 – Tuesday, February 9 at 10 am PST).
1) Digital Transformation: Why Building Trust Comes Before Deploying Tools
Trust is vital in the business world—even more than training and tools. However, all three matter and are remarkably interconnected. With trust at the forefront, cost savings (i.e., increased employee productivity and initiative) will trickle down, and personnel will be happier at work. But it all starts at the top with leadership.
2) Continuous Delivery and Release Automation for Microservices
As software organizations continue to invest in achieving Continuous Delivery (CD) of their applications, we see increased interest in microservices architectures, which–on the face of it–seem like a natural fit for enabling CD. In microservices (or its predecessor, “SOA”), the business functionality is decomposed into a set of independent, self-contained services that communicate with each other via an API. Each of the services has their own application release cycle and are developed and deployed independently often using different languages, technology stacks and tools that best fit the job.
3) Get Small to Get Big Through Microservices
If we trace a path that starts with Gutenberg’s use of moveable type to Malcom McLean’s invention of the shipping container, we start to recognize a very interesting pattern: Each new layer of abstraction and standardization creates tremendous value out of the resulting increases in scale and efficiency. Today’s digital innovators can trace a similar historical path that starts with mainframe computers and monolithic applications and then, step-by-step, reveals software’s interchangeable parts until we arrive at today’s cloud-based era of microservices and continuous integration.
4) The State of Containers: 5 Things You Need to Know Now
Docker adoption is up fivefold in one year, according to analyst reports. That’s an amazing feat: One year ago, Docker had almost no market share. Now it’s running on 6 percent of all hosts, according to a survey of 7,000 companies by Datadog, and that doesn’t include hosts running CoreOS and other competing container technologies. Most companies that adopt Docker do so within 30 days of initial production usage, the survey reports and almost all the remaining adapters convert within 60 days.
5) For DevOps Success, Embrace Culture Change
Out of the gate, I want you all to know that I’m not a tech expert. I’m happy that I’m able to navigate the typical business software and email on my laptop to get through my workweek. That said, at the Seattle Interactive Conference a couple of months ago, I attended a presentation by Lucas Welch, Director of Communications at Chef, a Seattle-based tech firm that provides an IT automation platform to brands such as Target, Nordstrom, and Facebook. Lucas’ presentation was on the topic of “DevOps.”
6) Microservices in the Real World
By @BenLinders | Published on @InfoQ
Alexander Heusingfeld gave a talk titled when microservices meet real-world projects at the GOTO Berlin 2015 conference. InfoQ did an interview with Alexander Heusingfeld and his colleague Tammo van Lessen about getting people from operations involved in architecture and dealing with “us vs. them” behavior when applying DevOps, what the Self-Contained Systems approach is and how it can be used to modernize software systems, similarities, and differences between the Self-Contained Systems approach and microservices, improving deployment pipelines and using measurements in deployment, and about his experiences with a “getting out of your comfort zone” program.
7) What’s the Difference Between DevOps and Continuous Delivery? By @Gidrontxt | @DevOpsSummit #DevOps
We live in an era of apps. More and more of our personal, social and work life is governed by apps. Communicating with one another through social apps, booking cinema tickets through your mobile device, or scheduling a business trip through the airline app. This digitization of services has arrived. Organizations that understand this sea-change have a unique opportunity to jump ahead of their competitors, acquire customers more quickly and grow revenues.
8) Using ARA to Achieve Higher Quality Software Releases
Application Release Automation, or ARA, is the process of packaging and deploying applications (or updates to applications) in an automated, repeatable and consistent way. In today’s market landscape software has become a major differentiator for many businesses, across all industries and verticals. In a world of apps, Internet of Things and customers’ expectations to be always connected, – just about every company is now becoming a software company. Software development is now critical to the success of your product, and its delivery process needs to be fine-tuned and streamlined to ensure that you get quality software in the hands of your end users as quickly as possible.
9) Will Microservices Make the ‘Ops’ in ‘DevOps’ Obsolete?
DevOps is a portmanteau of “developers” and “operations.” The concept of DevOps is about shifting IT culture in a way that enables developers and operations to work together more seamlessly. As more and more elements of DevOps become automated and leverage microservices such as container platforms, though, the operations side of that equation plays a diminished role.
10) Datical: Why DevOps is Right for Every Organization
For a concept which merges different stakeholders within a business, it is perhaps not surprising that recent research concerning DevOps shows a fractured landscape. 84% of respondents surveyed by Gleanster Research in August defined DevOps in a multiple choice poll as “developers and system administrators collaborating to ease the transition between development and production”, while 69% opted for “using infrastructure automation to facilitate self-service provisioning of infrastructure by development teams.”