StackState Blog

Mark Bakker

Mark founded StackState early 2015 together with Lodewijk Bogaards and the Xebia Group. Mark is a visionary and has been an IT architect/ engineer/ developer for over 15 years. Mark joined Xebia in 2007. Before joining Xebia he had a company in computers and networks for 8 years. In his spare time Mark has been chairman of a realty development trust which led in the development of 7 houses.

Recent Posts

Autonomy (in Dev/Ops tooling) does not equate loss of control

Posted by Mark Bakker on Aug 25, 2015 11:24:00 AM


Why are organizations moving to a Dev/Ops model of working?

In my opinion there is one main driver for this:

Bringing dev and ops (and – if possible – the business) together in a team helps the team to focus on their contribution to a specific business function in the company. There is no more need for specialization in the sense that the teams only do things based on specific technologies. Dev/Ops teams will now be able to really focus on business value. First this helps companies to become more agile and lean while constantly removing bottlenecks. Secondly Dev/Ops teams can make their part of the business work as smoothly as possible.

Having said so, how important is it that teams have the ability to support their part of the business chain? Should they all use the same kind of tools between different teams, just because there is some architect which tells them so? Or should they have their freedom in choosing the technologies/products their need to support their acquirements in the way they think is best?


Read More

Topics: Dev/Ops

The Monitoring Maturity Model explained

Posted by Mark Bakker on Aug 11, 2015 8:59:00 AM


The pace of change is increasing. Component sizes are shrinking. All the while monitoring solutions are bombarding us with log data, metrics, status reports and alerts. It all scales, but we don’t. How do we prevent from drowning in run-time data?


A lot of companies are facing the same problem. They have such a huge amount of data, but can’t get a total unified overview. When problems occur in their IT stack, they don’t know where it originates. Was it a change, an overload, an attack or something else? Based on our experience, we created the Monitoring Maturity Model. At which level is your company now?

Read More

Topics: Dev/Ops, ITSM

Smart IT monitoring and root cause analysis needs big data

Posted by Mark Bakker on Jun 26, 2015 12:30:00 PM


Our big data engine is ready. We are on track to change the way IT departments work and manage their IT operations.


To understand what happens in an IT stack, we need good in-depth data. And as we all know, we gather this data through all kind of systems. We monitor, measure and analyze how software applications perform, which new deployments we did, the changes we made in our architecture or the issues we have and are trying to solve. All these pieces together are part of a big jigsaw puzzle. And when you add business processes, services and infrastructure components including their dependencies and states, you get what we call Full Stack Chain Monitoring. Having a single real-time unified overview is an interesting approach since it gives insights to devop teams, architects or IT services managers how healthy their (part of) the stack is. And it is a great tool for root cause analysis since it immediately shows where actual failures or services interruptions originate from.


The next step is storing all this knowledge in a big database for IT operation analytics.


Read More

Topics: Dev/Ops

About StackState

A new way of working: we connect developers, operators and businesses through a unified view of the IT landscape and business processes. StackState is founded in 2015 spin-off from Xebia Group.

Join over 5,000 people from companies like eBay, American Express, Cisco, Tesco, ING and more who get our best new posts delivered via email. Subscribe below if you'd like to get it too:

Subscribe to Email Updates

Most Popular Posts