Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
51

Mainly DevOps is not a role (when used as such it's more a buzzword than a real role). DevOps is roughly an organization pattern aiming at breaking the silo between developers and sysadmins. The main goal is to build teams with devs and sysadmins (along with testers usually) responsible for a product (application) from its definition, architecture decisions ...


50

Artifactory is a product by JFrog that serves as a binary repository manager. That said very often one will use a 'artifactory' as a synonym of the more general binary repository, much like many people use Frigidaire or fridge to denote the refrigerator regardless if it is a Frigidaire brand or not. The binary repository is a natural extension to the ...


46

DevOps is about maintaining code, is that correct? DevOps is not "just" about code, or systems, or any one thing. DevOps is a very general term that covers all things related to software delivery. Site Reliability Engineering is a term popularized by Google. From this article https://landing.google.com/sre/interview/ben-treynor.html we can distill their ...


46

Randy Bias chronicles the history of the term stating that it probably originated in 2011 or 2012 when Bill Baker used the analogy when describing "scale-up" vs. "scale-out" architectural strategies. Bias adopted this into his presentations about cloud architectural patterns: In the old way of doing things, we treat our servers like pets, for example Bob ...


44

A big part of DevOps is making it possible to release very often. That comes with automated build, automated testing, etc. You can say that to achieve its goals, DevOps need to use automation to be efficient. Here's how DevOps and automation are related. DevOps is not just automation, there's more to it. Conversely, automation is not exclusively used by "...


41

Wikipedia's article on serverless computing provides a decent introduction to the topic: Serverless computing, also known as function as a service (FaaS), is a cloud computing code execution model in which the cloud provider fully manages starting and stopping of a function's container platform as a service (PaaS) as necessary to serve requests, and ...


33

A "Walking Skeleton" is a form of "proof of concept" of your basic architectural concept. Where a proof of concept typically focuses more on a single functionality, a "Walking Skeleton" is a minimalistic end-to-end implementation. A "Walking Skeleton" is not an outline of your concept (only a "skeleton") but is really executable and shippable (it can "walk" :...


31

Absolutely not! DevOps is all about breaking down the traditional silos (departments) in order to be more efficient. Better communication between teams, improved visibility and reliable and automated process are ways to achieve a better product. I used to work for a big media company where we would support an internal tool and develop public-facing ...


30

During development you generate a fair amount of different artifacts. These might include: The source code The compiled application A deployable package Documentation and potentially others as well While you could use a source control system to store all of them, it's usually massively inefficient, as source control systems are usually designed to handle ...


24

In my opinion, the DevOps culture come along with a methodology change toward Agile process management. ITIL is heavily aimed at a clear formalism of the process and the results and thus more adapted to a Waterfall model. This doesn't mean ITIL is incompatible with Devops, but usually this will be two separate process with different timelines. I mean that ...


23

TL;DR: You should never try to hire a DevOps Team There are essentially three most common roles to hire for: DevOps Architect / Evangelist DevOps Engineer CI/CD Engineer These roles are distinct from your 6 essential software development roles that traditionally compose the software engineering organization: Product Management Software Development Tools ...


20

Continuous delivery and continuous deployment both take continuous integration one step further, by adding a 'deployment to production' step to the process. The difference between continuous delivery and deployment is that for delivery this step is done manually and for deployment is it automatic. Difference between Continuous Integration, Continuous ...


19

The very first thing to know about a container is: It is, first and foremost, a process. Once that is understood, one can start to understand how containers compare and contrast with virtual machines. Containers and VMs both share isolation from their hosts. The method of isolation is the critical difference. Container processes use extensions to the OS ...


18

Short Version DevOps a combination of organisational culture, Agile/Lean ways of working and software automation that when applied to Systems Administration and Operations allows these functions to operate with the same level of Agility as Agile or Lean Development Teams. Long Version The ideas behind DevOps came out of the Systems Administration, ...


18

Dave Swersky already posted an excellent response above with Ben Treynor's definition of SRE, which is as poignant today as it was in 2003. Fundamentally, it’s what happens when you ask a software engineer to design an operations function. So, in an attempt to further define "DevOps", here's an excerpt from the book Effective DevOps by Jennifer Davis &...


17

Immutability is a term often used in computer science circles, which generally boils down to "not possible to change after creation". It is typically used in reference to parallelism, concurrency, and thread safety. The discussion of that topic is fascinating, but can generally be found elsewhere on Stack Overflow. I'm resisting the urge to dive into it ...


17

Wikipedia has a very good answer to this question. Artifact, sometimes also called Derived Object, is a product of some process applied to the Code Repository. Originally they were called Build Artifacts, but as more processes were applied other than build to create them, the first word was simply dropped. The major distinction is that artifacts can be ...


16

To add to Richards answer, generally the analogy is helpful in terms of considering the impact of the loss of a server. If you would feel some sort of distress over the loss of any individual piece of infrastructure, then consider it a pet (read antipattern). If you would feel pretty comfortable knowing that if any of the fleet stopped functioning there ...


15

Automation is a key attribute of DevOps, but it's not the full story. The question is kind-of like "What's the difference between time-boxing and Scrum?". You'll hear DevOps called a 'culture', a 'movement', a 'methodology', and all kinds of things that won't box it in well enough for you to understand it, even though those descriptions are accurate. In a ...


15

Martin Fowler has a good overview: https://martinfowler.com/articles/serverless.html TL;DR "Serverless" describes application development and architecture that designs applications in which the infrastructure is ephemeral, meaning that they tend to be container-based and can "come and go" based on a dynamic scaling mechanism. This prescribes the use of ...


14

I need to put my answer to this question in the context of what DevOps is, more specifically within the DevOps transformations I have been part of, DevOps is the ownership of the full Software Development Lifecycle. All of the practices in the chart are an important part of DevOps, and they enable and underpin both Systems Thinking and Amplification of ...


14

'Serverless', like many things in our space, is becoming an overloaded term.. but generally what it means is "Functionally, Our architecture does not depend on the provisioning or ongoing maintenance of a server" The first instance that comes to mind is a single page javascript app, that uses local storage, and is stored on something like Amazon S# or ...


14

Site Reliability Engineering falls under more or less traditional operations, but heavily automated and version controlled, what is also called Infrastructure as Code. It is a well defined vertical role. In modern DevOps this is the vertical slice that relates to Operations. You can have a team of SRE. DevOps as such is a cultural change for an organization....


14

I'd agree this is a buzzword as much as DevOps can be. Main task of a SecOps added on top of an usual operational engineer tasks is to take the burden of following CVE publication feeds, handling the remediation, usually handling things historically handled by the security or network administration team (Firewall rules, Web Applications Firewall exceptions) ...


14

I think you would be hard pressed to get a straight definite definition of a Platform Engineer. Where I'm currently positioned everyone on the team starts out with their own special role but very quickly the end-game seems to be to feel comfortable enough to be called, or to call ones self, a platform engineer. When I was first told that officially a ...


13

My team and I are responsible for developing "one-offs", products that once finished are given to the client for upkeep or in some cases managed by us for a fee. We still need to maintain a solid development pipeline to handle the constant feedback from our clients in order to ensure that we ship them something reliable and proven to run. While the ...


13

DevOps is really a cultural shift - it's intended to be about breaking down the traditional barriers between operations and development (and really also with QA and the rest of the business!). The idea is that rather than having departmental 'silos' you can work directly with other teams to get things done quicker and more efficiently. It's all about ...


13

Without repeating the content of https://martinfowler.com/articles/feature-toggles.html, since it is an amazing in-depth explanation on what feature flag toggles are. I will just focus on the DevOps aspects. According to the 2014 State of DevOps Report prepared by PuppetLabs, there are four major metrics to measure IT performance: Lead time for changes ...


12

DevOps in a nutshell From Wikipedia: 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 ...


12

Instead of Continuous Integration and Continuous Delivery, I would define the definition of done as "Active Continuous Improvement at all levels of the organisation". The other topics like automated builds, CI/CD, etc... these are just milestones and most definitely not the ultimate goal for the organisation in its DevOps efforts. It does look like it ...


Only top voted, non community-wiki answers of a minimum length are eligible