Win a copy of Spring Boot in Practice this week in the Spring forum!

Len Bass

Author
+ Follow
since May 18, 2015
Cows and Likes
Cows
Total received
5
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Len Bass

We called it "A Software Architect's Perspective" because we are software architects and that is what we bring to the party. The target audience are architects and developers who are wondering how DevOps will impact them. There is a chapter on building a business case that should be of interest to project managers but the book by Humble and Farely on continuous delivery is much more targeted to project managers.
7 years ago
No we have no outsourcing case study. One technique used in continuous deployment is to decouple teams. If teams do not communicate directly then the face that they are distributed should not affect development. The fact that a portion is outsourced (I assume through some sort of contracting mechanism) means that there might be some contractual barriers to adoption. I haven't read anything about such problems but its an interesting topic.
7 years ago
Tes 0 tgere are kits if things to take care of both on the process side and the organizational side. We have a chapter in our book that describes how one builds a business case for DevOps and another, case study, chapter about an organization that implements continuous delivery pipelines. These chapters will answer some of your question. What it leaves out are the cultural issues. These are covered in LinkedIn DevOps groups among lots of other places.
7 years ago
The goal of DevOps is to reduce time to market. If your organization wants to reduce the time to market for its products, then DevOps processes should be considered. It then becomes a cost/benefit trade off where the benefit comes from the reduced time to market and faster recovery from errors and the costs are personnel/tools/organizational change.
7 years ago
You had a couple of questions.

1) what is the difference between now and 19 or 15 years ago? The difference is that a) operators and their responsibilities are getting much more visibility that they had 10-15 years ago. Partially because their job has gotten much more difficult. and b) the tools to support various deployment and continuous deployment pipelines are astounding and continue to improve.

Your second question is are there situations where DevOps is not appropriate? The answer is, of course. Continuous delivery and deployment assume that all tests can be automated and that errors in production can be found and fixed relatively quickly. This is not the mind set I would want for someone designing a nuclear power plant or an aircraft flight control system.
7 years ago
The goal of a microservice architecture is to de couple the work of development teams so that they can deploy without spending too much time on coordinating over libraries, versions, and technologies. This is done using message passing as the sole communication mechanism between components. The drawback to using a microservice architecture is that you need to pay careful attention to performance with the message passing.

I participated in a workshop on microservices at the recent SATURN conference (as well as a mock trial where microservices were accused of being an attractive nuisance). The prosecutor was Simon Brown and the defendant was Sam Newman. I was the judge. The output of the workshop can be found here https://github.com/michaelkeeling/SATURN2015-Microservices-Workshop and the mock trial was videotaped and that should be online relatively soon. Sign up for SATURN 2015 notifications to be notified when the video is available.
7 years ago
The goal of DevOps processes is to reduce the time between commits and an application running normally in production (with high quality). A place to start is to benchmark your current operations. How long does it take between the time a developer commits code and it goes into normal production? How many How long does it take to clear application specific tickets? Are these acceptable numbers? You have to convince the powers that be that a) those numbers in your organization are too high and b) introducing some new processes will improve the situation. Propose a pilot in conjunction with a Dev team that you can use to test out the cost/benefit of some of the DevOps processes.
7 years ago
No - this book is not designed to describe how to use any particular tool. There are lots of good tool specific books (or online materials) that describe tools. This book is intended to deal with knowledge that developers should know about design and requirements that eminate from using DevOps processes.
7 years ago
In some organizations - e.g. Google - developers are responsible for their component - its correctness and its meeting its SLAs. There is another group (SET in Google) who are system testers. They are responsible for overall system health - latency, etc. These are the things that are not strictly associated with a single component. Interpreting monitoring information relative to system performance (not single component performance) is their responsibility.

7 years ago
The answer is both. It helps to have high level buy in up front because you will need to justify your use of resources to implement the DevOps processes. But it also helps to start small with a pilot to demonstrate what is possible.
7 years ago
One model is to have a DevOps team that is responsible for the tools and then each Dev team uses and configures the tools. This means the Dev team is responsible when it breaks. The help from the DevOps team is in the nature of an initial set up but not continuing support. It sounds like this is your situation. If your organization is large enough then the DevOps team might have training and help sessions but this depends on how pervasive the problems with using the tools are and how many Dev customers there are for each tool.

It helps if the DevOps group has a clear set of roles and responsibilities and then are staffed so that they can fulfill them.
7 years ago
In this case, I don't think the questionis speed. The question is cost. How much are the dedicated environments going to be used and are you willing to pay the price for their ideleness?
7 years ago
DevOps is a collection of processes intended to shorten the time to deployment from code commit. The question is "does putting ant tasks in a build.xml file shorten the time to deployment from the process it replaces?"
7 years ago