I was late to this seminar due to talking a little too long about NServiceBus with Sean Farmar at Particular Software booth. When I came into the seminar a Continous Delivery book was on the screen and the speaker was way beyond the introduction. Two other books are shown during the talk, the classic Domain Driven Design by Eric Evans and Implementing Domain Driven Design by Vernon Vaughn.
Mr. Ford talks about how a continous delivery pipeline must be constructed with steps such as commit, functional test, user acceptance test staging and so on. This increases confidence and gives feedback at the different stages. There are no rules for constructing the pipeline but it is up to the architect.
Mr. Ford states that today’s best practices will be tomorrows anti-patterns and goes on to show that the increasing complexity of problems drivers architectural change. The most certain thing is that the code will change and the design should make that simple. The talk continues with tackling some of the problems for constructing the component pipeline.
During the lecture only two tools are mentioned Structure 101 and NDepend and they are used to analyze the dependencies in the code base. The reason these are brought up is to avoid creating dependency cycles. Structure 101 is for java and NDepend does somewhat similar job for .NET. Diamond Dependencies are also a anti-pattern that complicates constructing the pipeline.
Mr. Ford continues the seminar talking about domain driven design and some of the problems with building a micro service design. He brings up the Fallacies of distributed computing as an example of the problems that must be considered when moving form a monolith to a micro service design.
A pretty intense talk considering it was the first one of the day. Mr. Ford speaks well and moves quickly between the topics, definitely worth the visit.
No comments:
Post a Comment