Stemlaur, blog !

TECH | Three DDD stories

In this article, I will tell you 3 real-life examples where Domain-driven design practices could have helped teams avoid lots of confusions and waste of time and money. These stories feature: 👔 The Business Guy 💻 The Developers 🤦 The Facepalm 1. Taking words into account 👔 The business guy comes to 💻 the developers to implement yet another great feature described with those words: We want to implement the user account, so people can...

TECH | Architecture decision record (english version)

Architecture Decision Records (ADR) is a little-known technique in the living documentation palette, it centralizes and makes explicit a set of architectural decisions made over time, capturing the context and their possible alternatives. It complements the documentation very well with the code when these decisions concern the evolutionary architecture of your project. An ADR1 can be local (within a component), or global (within an IT department). Why did we choose to use Hibernate? Why did...

TECH | Stop using JPA/Hibernate

EDIT 1: I replaced most of the pronouns “he” by “they” to make the article more inclusive EDIT 2: I improved the article, thanks to your awesome feedbacks, thank you very much Introduction 🐈 15 years of that, during my master, a teacher taught us a new technology, allowing, I quote: You will not have to write SQL queries anymore! If you are like me, and you hate writing SQL queries you are going to...

TECH | Architecture decision record

Architecture Decision Records (ADR) est une technique méconnue dans la palette de la documentation vivante, elle permet de centraliser et rendre explicite un ensemble de décisions d’architecture prises au fil du temps, capturant le contexte et leurs alternatives possibles. Elle complète très bien la documentation par le code quand ces décisions concernent l’architecture évolutive de votre projet. Un ADR1 peut être local (au sein d’un service), ou global (au sein d’une SI). Pourquoi choisir Quarkus...