He is a Principal Consultant at ThoughtWorks, where he has been for over seven years. He has worked with a variety of companies in multiple domains, and currently runs the Cloud & Continuous Delivery Practices for Europe. He has written articles of O'Reilly, presented at conferences, and sporadically commits to open source projects. Principally a Java developer, he also spends lots of time with Clojure and Python, and build systems that hate him.
We have lots of information available about our systems. CPU, disk IO, orders placed, error rates, users logged in. But typically all these pieces of information are collected, aggregated and stored in very different ways making correlation difficult and increasing the operational overhead of our systems. What if we could treat all of this information as events? What if we could aggregate, store, and report on all of this information as a uniform event stream? This talk will look at emerging trends in the space of log aggregation, monitoring and event streaming to paint a picture for how you too can start to make real use of the information already available to you using nothing more complex than some free, off the shelf Open Source software.
Lots of people are talking about Micro Services. But how micro is micro? And while we're at it, what is a micro service anyway? This session will briefly introduce the concept of microservices, and why they are important. But then we'll focus on the tough questions. If you're starting with a big, monolithic system, how should you split it up? When are microservices right for you? This talk looks at the competing forces from Conways law to Operations, which can help you make the right decisions about service granularity and just how 'micro' you should go.