Whether you call it SOA or microservices, one consistently important design principle in service architectures is Service Autonomy. At first sight it seems a short sound-bite that’s easy to implement. That is, until you actually start doing it. It turns out there are actually many aspects that account to service autonomy. When looking at it in closer detail you’ll notice there are different types of autonomy. In this talk I’ll go over the different types of autonomy that matter when developing a (micro-)service. Furthermore I’ll provide some practical advice on how to implement these different kinds of autonomy and how it fits in with other design principles.
Jaap is a Java developer and architect for jstack with more than 10 years of experience in Java development in various environments. He’s passionate about Java and Open Source technology and likes to combine architectural work with hands-on development. He loves sharing knowledge and experience with colleagues and like-minded people. Outside IT he loves playing board-games with friends and colleagues.