Florian Herlings.

This was sent out as a newsletter on 04. October 2019. Please feel free to sign up to get future updates delivered to your inbox automatically.

Architecture Patterns, clean code, the importance of sponsorship and more…

Hello there,

October is here and I am so happy to be back with a few helpful links. As always, I am very much looking forward to your feedback via twitter/__florian of this early bird edition. Let’s dive in!

„Solutions Architecture Patterns” by Chanaka Fernando

Great collection about solution architecture patterns like Service Mesh or Anti Corruption Layer, including detailed descriptions, diagrams and suggestions on when to use them. A lot to read, but even if you just skim most and go in depth on some things it is very much worth your time.

„Best Practices for Event-Driven Microservice Architecture” by Jason Skowronski

The article gives a great high-level overview on the event-driven microservice architecture, and what you need to consider when implementing it. Jason does not go into too much detail, but is a very good reference to get into the topic.

„A few principles of clean code” by Thomas de Moor

Thomas gives a good overview about some principles that you and your teams can adopt to write cleaner code. This quick read will work perfectly as a pre-weekend reminder, that you could send out on a Friday afternoon. ;)

„What does sponsorship look like?” by Lara Hogan

A wonderful article about the difference between mentorship and sponsorship, and the impact we can have by applying the right one to the right situation.

To sponsor someone is to feel on the hook to help get someone promoted. It is raising up the name of someone to help them get more opportunities to do visible, valuable work. It is not just giving advice and mentorship.

„Organisational Dysfunctions Mirrored as Architectural Complexity” by Nick Tune

Great article, that has been sent to me by many people. In short, Nick describes that sometimes there is a big difference between being accountable and being responsible. He goes into detail about the impact it can have on your architecture if you don’t manage it properly.

We should stop and frequently ask ourselves: Are we trying to architect around organisational dysfunctions? Are we exacerbating the problem?

Thank you for reading and have a wonderful weekend!


This website does not use any tracking or feedback mechanism. Instead, I would love for you to get in touch with me to let me know if you liked it or if you have any suggestions or questions.