The second part of the post discusses supportive services. Supportive services support (as the name implies) business microservices. Moreover, they can be used to build an efficient and not boring environment, by avoiding implementing the same thing several times. Samples are given which can be implemented as supportive services. In the end stands a proposal … Continue reading Supportive Services
Microservices are a good architecture principle. But to tailor them seems quite difficult and it’s discussed widely over the community. The post discusses the possibility to create microservice along a business process – whereas one business process step is one microservice. “The term "Microservice Architecture" has sprung up over the last few years to describe … Continue reading How to tailor microservices?
The post discusses, how estimates can be given at an extremely early stage of a project. A specific form of planning poker is proposed including some kind of risk estimation. I think, everyone who works in some role in software industry has done some estimations. If you were on the lucky side, you could do … Continue reading Estimations without any Expertise
German Version Over the last months I’m thinking more and more about, how architectural work can be done agile. Of course, I know the standard answers: architecture is done by the team, use a KANBAN boards, involve stakeholders, … But I think the problem is deeper as architects who aren’t integrated in teams can’t be … Continue reading Is Enterprise Architecture and Agility a Contradiction?