James Turnbull: Tooling Moving From Host-Centric to Service-Centric



This is the third excerpt from James’ podcast around what’s future tooling going to look like.



Tom Parish: What comes next after the current crop of tools?


James Turnbull:  So I think the current crop of tools are very host-centric and Puppet is one of those. It’s very much focused on configuring a node. There are some more tools that have come along like MCollective that are much more based on some sort of orchestration and understanding the interconnection between things and it triggering one event in one system and seeing its impact on another. So I think that’s where tooling is going. 



So I think the next step is tools that are service-centric because the business doesn’t really care about hosts. I mean, they don’t really care about the widgets you buy.



Tom Parish:  Right.



James Turnbull:  They care about the service they deliver.



Tom Parish:  Yes.



James Turnbull:  And so you probably shouldn’t really care about those hosts either.  You should really care about the end-to-end service.


The next generation of tools that people are building now are much more about understanding how do I make a change in my environment and what’s the impact to the actual service. Cloud is another aspect of that because with cloud you don’t really need to worry so about scaling.


You still have to worry about architecting solutions and things like that in a sort of performance sensible way. But the cost to have a thousand machines versus a hundred machines in EC2 is significantly different from the cost of physical plant. 



So you know you have that sort of scale then those considerations sort of go away and you start to think about, you know: what am I looking at here?  I’m looking at the end-to-end transaction speed or I’m looking at the availability of this whole service, you know, a web front-end and database back-end and some middleware and maybe integration with other services.  That’s what I should care about. Not machine database one [because] database one is just a component.




Coming up next: DevOps gets focus on the customer.

Share This Post