Building Developer Services with Habitat

Something we often talk about in the arena of DevOps is the need for cultural or organizational change. One thing that’s often missing from the conversation is the virtuous cycle that tends to occur between People, Process, and Technology. As DevOps has helped us rethink our processes and organizations, technology has advanced and changed under us. Architectural patterns also have changed, and are made easier to achieve by the technology changes. A great example of this is the relationship between Microservices (architectural pattern) which is made possible/easier by containers (technology). And then as the architecture and technology changes, this influences how we can organize our teams (Conway’s Law), and how we can change our processes.

One change we’ve seen come about through this cycle is the notion of “Shared Services” teams becoming obsolete. Gone are the days of tickets and email. Rather development and product teams want to request services via an API or some automated fashion. Shared Services teams rather need to morph into “Developer Services” teams to quickly provision and run the services development and product teams require.

On this recent Chef webinar, we talk about the challenges facing these Shared Services teams, how consumption models have changed, and the rising world of Developer Services. We also show you how Habitat, Chef’s Open Source project for Application Automation, can help you build and run the services development teams require to get their job done.

Interested in Habitat? You can learn more at the project’s site, check out recent blog posts about Habitat’s underlying technology, or join the vibrant and growing community.  

Michael Ducy

Former Chef Employee