Welcome!

@DevOpsSummit Authors: Dalibor Siroky, Pat Romanski, Elizabeth White, Liz McMillan, Stackify Blog

Related Topics: @DevOpsSummit

@DevOpsSummit: Blog Feed Post

DevOps 101 - Integration By @JoePruitt | @DevOpsSummit #DevOps

DevOps integration targets quality testing, feature development, and product delivery

In my previous articles on the history of DevOps, I’ve outlined the following pillars of the DevOps methodology

  • Management
  • Integration
  • Communication and information sharing
  • Collaboration
  • Automation
  • Measurement

DevOps-Integration

The Second Pillar
The second pillar in the DevOps stack is that of Integration.  DevOps integration targets quality testing, feature development, and product delivery.  Integration, or more specifically, Systems Integration is the process of linking together different computing or component systems and software applications physically or functionally to perform as a single consolidated unit.

Systems integration requires a wide skill set in areas such as network architecture, protocols, systems, software engineering, documentation and communication.  A DevOps Engineer needs to have a unique skill set that combines that of both the traditional software developer with that of the IT engineer.  Typically DevOps engineers are either developers who get interested in the deployment process of their applications or system administrators who have a passion for scripting and software development.

The Methods of Systems Integration
System integration traditionally falls into three methods.  Vertical, Star, and Horizontal (or Enterprise Service Bus).

Vertical Integration
Vertical integration involves integrating systems according to their functionality by creating functional components referred to as silos.  One of the key benefits of this method is performed quickly and typically is cheaper in the shorter term.  But, a negative to this methods is that the cost of ownership is often higher and scaling the system would likely require implementing another silo.  Also subsystem reuse for new functionality is often not possible.

Star Integration
Star (or Spaghetti) Integration is the method of integration where multiple systems are interconnected to each other (like a plate of spaghetti).  The cost varies depending on the types of interfaces the system use.  Costs and time are greatly increased when adding additional systems.  This method is very flexible and provides high levels of reuse.

Horizontal Integration
Horizontal Integration (or Enterprise Service Bus) is a method where a dedicated system is used to communicate to other subsystems.  This allows for only one connection per subsystem to the service bus and the ESB translates the interface to a different system.  With this method, it is designed to allow for you to replace one subsystem with another easily by updating the ESB with the new systems interface.

Conclusion
Integration is just one piece of the DevOps puzzle.  In my next article I’ll discuss how communication is integral in the DevOps process.

More Stories By Joe Pruitt

Joe Pruitt is a Principal Strategic Architect at F5 Networks working with Network and Software Architects to allow them to build network intelligence into their applications.

@DevOpsSummit Stories
ChatOps is an emerging topic that has led to the wide availability of integrations between group chat and various other tools/platforms. Currently, HipChat is an extremely powerful collaboration platform due to the various ChatOps integrations that are available. However, DevOps automation can involve orchestration and complex workflows. In his session at @DevOpsSummit at 20th Cloud Expo, Himanshu Chhetri, CTO at Addteq, will cover practical examples and use cases such as self-provisioning infrastructure/applications, self-remediation workflows, integrating monitoring and complimenting integrations between Atlassian tools and other top tools in the industry.
"Storpool does only block-level storage so we do one thing extremely well. The growth in data is what drives the move to software-defined technologies in general and software-defined storage," explained Boyan Ivanov, CEO and co-founder at StorPool, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and cost-effective resources on AWS, coupled with the ability to deliver a minimum set of functionalities that cover the majority of needs – without configuration complexity.
As Marc Andreessen says software is eating the world. Everything is rapidly moving toward being software-defined – from our phones and cars through our washing machines to the datacenter. However, there are larger challenges when implementing software defined on a larger scale - when building software defined infrastructure. In his session at 16th Cloud Expo, Boyan Ivanov, CEO of StorPool, provided some practical insights on what, how and why when implementing "software-defined" in the datacenter.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, which can process our conversational commands and orchestrate the outcomes we request across our personal and professional realm of connected devices.