Lesson 113 - Cart Before The Horse AntiPattern

Although anti-patterns are usually associated with software development, there are plenty of them in software architecture as well. An anti-pattern is something that seems like a good idea at the time, but can lead you down a bad path. In this lesson Mark Richards talks about the Cart Before The Horse architecture anti-pattern. Through conversations between a product owner and software architect, he describes what this anti-pattern is, how it occurs, and then describes techniques for avoiding this all-to-common anti-pattern.

Reference Links:

[vespeerr]

Hello Mark, really thanks a lot for your videos. Do you have a plan to discuss Data Mesh ? I mean not just the canned principles people are regurgitating but the actual implications, failure modes etc ? That would be great

[jimitshah]

What are server sent events pros and especially cons(couldn't find much contents related to cons). How to scale them?

[MrAnanthnarayanan]

Hi Mark,
Thanks for the lesson. Since it process large volumes of data and sometimes could be memory and cpu intensive, won’t that bring down the whole system if at all there’s any issue? My only concern would be: adding new features to existing monolith also shouldn’t bring the monolith down, in turn almost the whole system down. Is micro-kernel differs from this?

[chris-ryan]

I know a couple of one trick pony architects who go round rubber-stamping their favourite stack /solution onto companies before gathering and evaluating requirements.

[vishnumv]

Silly question not related to this video, how we can decide the best way to arrange the microservices in a repository? What would be the ideal approach when the number of services go up?