Bits and bobs

Agile has been around for a while now, and has been proven to be tricky to implement and returns questionable value. I have seen lots of different forms of agile, and sometimes the ceremonies get all the focus, and the essence of agile is lost. Especially for big corporates, they need to scale out this approach, so it becomes a playbook of steps you need to do. As we move into microservices, adopting agile was a critical aspect. Being able to change direction or approach means microservices can evolve as we go, rather than being predefined right at the beginning. This is an extrealmy important aspect of microservices. Generally in a monolith, the patterns are established and followed without question. Changing a pattern is hard, and needs commitment, and understanding from everyone. Microservices on the other hand, mean every domain can use a different pattern, and we can grow and develop the right pattern as we go. Whereas a change like this is massive in a monolith. Test and l...

It's been a while since posting something, but I feel like I would like to add to the millions of posts about microservices. I was considering avoiding adding to the already overpopulated mess of microservices articles, but I thought what the hey. I work for a large retailer in Australia and we were having a few issues with our platform. The very first step was to identify what exactly was our problem and to make sure we chose a path which would alleviate some of those problems. We had some technical problems, but we also had a bunch of business ambition which needed to be achieved along the way. Lets never forget, it the business which drives our decision right? There is a buzz around microservices at the moment. But it's important to understand your problem and make sure it is the right approach. The problems we had were Scalability Availability  Dependancies Domain knowledge Experimentation Long deployment cycles  Scalability The problem we had with scalabi...