Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: @DevOpsSummit, Microservices Expo, Containers Expo Blog

@DevOpsSummit: Blog Feed Post

Microservices and Containers | @DevOpsSummit #DevOps #Microservices

Microservices are where it’s all going and Container systems like Docker or Kubernetes are a huge enabler of that vision

Microservices, Containers, Code Ownership, and Continuous Support
By Todd Vernon

Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco.

Small Image: Courtesy Akana, Inc

Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.

Spoiler Alert: Microservices are where it’s all going, Container systems like Docker or Kubernetes are a huge enabler of that vision, code ownership flourishes in this environment, and DevOps promotes this culture and ecosystem of tools that unlock the huge social gains of all of it.

Let’s unpack that long sentence a bit.

Microservices are not a new concept, they existed a decade ago by another name, Service Oriented Architecture (SOA). The idea of SOA, and now Microservices, was to break up huge monolithic software architectures into more easily adaptable parts that are loosely coupled and easier to implement. It was good idea then, and is still a good idea today. However, SOA died in actual practice because it lacked lightweight frameworks to successfully implement it. In addition, Agile methodologies as a development philosophy were still a bit immature to successfully drive the development of these services. Huge monolithic projects, largely remained huge monolithic systems. In the end, the time just wasn’t right and the lift was too great.

Fast forward a decade. The modern implementation of microservices, powered by a lightweight messages passing via http with json bodies, coupled with short development sprints of a now mature Agile software development process is allowing new more powerful ways to decouple systems in an iterative way. This time around the technical gains will be huge, as will the social gains (more on this later).

Continuous Integration (CI) and Deployment (CD) are also enabled by microservices. Since a properly designed microservice implements a small well defined functional contract, exposed only through its external API, it’s easier to build comprehensive automated tests for that specific service. This allows developers to change, test, and release code more quickly and frequently without worrying about the effects on the rest of the system.

Technologies like Docker and Kubernetes are the natural delivery vehicle for microservices. Code as Infrastructure has been around for a while, but the ability to really control the instantiation and discovery of large groups of microservices is a bit of a reach for Hypervisor based VM based cloud systems. When a microservice meets container technology, the level of empowerment for software engineering is pushed to a new level. Using these two concepts architectures will really be living breathing entities, and much more adaptable than in the past.

Social aspects of software engineering are the hidden gain. With the ability to essentially build Lego blocks of code with small understandable functional purpose, it is now possible for an engineer to actually own a piece of code from requirements to deployment and through to production. In large monolithic systems ownership of a ‘part’ was historically impossible. What you don’t own, you care less about. Therefore, if an engineer has ownership and can attach their own personal brand to a part of the system, the quality of that part will be an order of magnitude better.

DevOps is unlocked. DevOps in large part is the social contract engineering has with the broader business. Software is eating the world, and SaaS platforms are on the forefront of the meal. Where SaaS businesses used to have huge Network Operation Centers (NOC’s) to deal with system problems with leagues of humans at the ready to respond to problems, more Agile businesses have recognized that pushing new code into production multiple times a day has literally rendered the NOC useless. In order to support today’s systems, you need to involve the person that wrote the code. NOC’s were built to repetitively solve common problems that by necessity persisted in complex systems. The reality of today’s world is that problems are different everyday and problems that used to wait until the next release, are now fixed the same day and redeployed.

And at this point, the story comes full circle. A person that writes a part of a complex system, attaches his/her brand to that part and is both proud of it and happy to address a problem when it arises. Microservices have an inherent social aspect to them as the entire team is responsible for their behavior. A positive side-effect of this is that the general stress of being “on-call” is much less when the problem being delivered to you, by a product like VictorOps, is inherently known to you; because you know the inner workings of how the code was designed to work.

Every individual technology and part are interesting in their own right. However, the sum of the parts is a very compelling view of the future. A future, where devs are given the power to release quickly and often, and to holistically own their code; from requirements to production. It is my belief that microservices, containers, and above all DevOps will work together to usher in this new reality by bringing it into present day focus.

Special thanks to:
Chad Arimura, CEO and Co-founder of Iron.io  @chadarimura
Eric Knorr, Editor and Chief, @InfoWorld
Barunch Sadogursky, Developer Advocate, JFrog  @jbaruch
Jos Bourmans, VP of Technology Operations, Krux   @jiboumans
Jordan Dea-Mattson, Chief Architect DevOps PM  @jdeamattson
Leonid Igolnik, VP of Engineering, CA Technologies
Aniket Kulkami, Director of Cloud Engineering, @Box
PJ Kimer, CTO and Co-founder, Illumio   @pjkirner
Mark Nelson, CTO Concur.  @MarkTNelson

The post Microservices, Containers, Code Ownership, and Continuous Support appeared first on VictorOps.

More Stories By VictorOps Blog

VictorOps is making on-call suck less with the only collaborative alert management platform on the market.

With easy on-call scheduling management, a real-time incident timeline that gives you contextual relevance around your alerts and powerful reporting features that make post-mortems more effective, VictorOps helps your IT/DevOps team solve problems faster.

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.