Microservices are popular with many teams. But, software development patterns are still in flux around this architectural pattern. In the last se...
For further actions, you may consider blocking this person and/or reporting abuse
Hey James, great post! I hope to take some of these tips on board with my current project. You mentioned that "Without specific practices to manage these tendencies teams can become insular and territorial". I have seen these issues first hand even within a single team (one person will build a service then they are shackled to that for life) do you have any suggestions of specific practices people could follow to help avoid these issues? Simply doing cross bounded context MRs? or are there some other tricks of the trade to use?
I am a big fan of Extreme Programming and think some of the practices that come out of that can be really helpful. Specifically I would look at pair programming and team rotations. Team rotations gets more tricky as a team gets larger and if technology diversifies. That would be my most immediate thought for how to counteract the negative effects that microservices can introduce.
I agree, I can see in our own projects, a lot of time is spent in redefining the need, again and again. Not that is should be perfect from the start, but sometimes critical business decisions are taken after 2 weeks of development, and this greatly reduce our performance.
So I would say definitively, teams needs to sit down and think first. And also, not hesitate to draw, to make schemes, write a lot of use cases...
Boasting a heritage of distinction over an extended period, our renown stands as proof of our resolute dedication to delivering top-tier garage door repair services in Yorktown, VA, and its surrounding locales. As Fixing Garage Door Problems your reliable ally, we offer an unwavering assurance to swiftly address your requirements, ensuring the resolution of your garage door concerns with effectiveness and attentiveness.