#evolutionaryarchticture

[gfader]

How do you transition to a Microservices Architecture? via @randyshoup

Randy has a great answer on minute 22:00.

“The only thing a Big Bang migration guarantees is a *Big* Bang.”

Don’t use a BigBang approach.

Rather extract, consume, migrate data, rinse and repeat.

When you have a Microservice Architecture, you have new problems and Randy helps you with those.

And Randy also answers the Why of Microservice Architecture and lots of other great detailed questions at the end.

Watch yourself: 1:06h

Managing Data at Scale: Microservices and Events - Randy Shoup January 2018 https://www.youtube.com/watch?v=tkxJk01Wz6Y

[gfader]

Do you know the difference between a desirement and a requirement? via @ElegantCoder‎

Great article from David about "evolutionary architecture" and a nice example about it from the Microsoft Word ribbon.

David explains desirements and requirements as:

A desirement is a non-compiled request for software to change. Examples include specification documents, Team Foundation Server Work Items, index cards, and hope expressed with Microsoft Word.

Everyone can state a desirement and throw it on the bottom of the wishlist. The interesting part is when a desirement gets closer to be a requirement (bubbles up) and the team discusses about the details and writes acceptance tests with the business to confirm them. 

A requirement, on the other hand, is an automated test proving desired behavior exists in software. Requirements (tests) must pass before software may ship.

This leads to creating a ATDD Ready Backlog, which is a great way to make sure you have "always releasable software".

Full article from David Starr: http://visualstudiomagazine.com/articles/2013/01/07/leveling-up-agile-requirements.aspx