SE# DevOps

Coming Soon …

DevOps (a clipped compound of “software DEVelopment” and “information technology Operations”) is a term used to refer to a set of practices that emphasize the collaboration and communication of both software developers and information technology (IT) professionals while automating the process of software delivery and infrastructure changes (#)

DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market. (#)

DevOps – Venn Diagram

A Venn diagram (also called a set diagram or logic diagram) is a diagram that shows all possible logical relations between a finite collection of different sets. (#)

Illustration showing stages in a DevOps toolchain

DevOps – Development and Operations (*)

Open source development

Open source development is an approach to software development in which the source code of a software system is published and volunteers are invited to participate in the development process. Its roots are in the Free Software Foundation, which advocates that source code should not be proprietary but rather should always be available for users to examine and modify as they wish. Open source software extended this idea by using the Internet to recruit a much larger population of volunteer developers. Many of them are also users of the code.

The best-known open source product is, of course, the Linux operating system which is widely used as a server system and, increasingly, as a desktop environment. Other important open source products are Java, the Apache web server and the mySQL database management system.

A fundamental principle of open-source development is that source code should be freely available, this does not mean that anyone can do as they wish with that code. Typical licensing models include:

  • The GNU General Public License (GPL). This is a so-called ‘reciprocal’ license that means that if you use open source software that is licensed under the GPL license, then you must make that software open source.
  • The GNU Lesser General Public License (LGPL) is a variant of the GPL license where you can write components that link to open source code without having to publish the source of these components.
  • The Berkley Standard Distribution (BSD) License. This is a non-reciprocal license, which means you are not obliged to re-publish any changes or modifications made to open source code. You can include the code in proprietary systems that are sold.

დამატებითი მასალა:

  • IBM DevOps #1, #2, #3, #4
  • Agile DevOps #1
  • The Four Keys You Need To Achieve Strategic Agility #
  • Digital Magic: Disney’s DevOps Transformation #1

One thought on “SE# DevOps

  1. Pingback: SE#10.1 System Dependability | IN@TIMES

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s