2023
Personal
Next Js
Tailwindcss

The context

This is my very first experience with clean architecture. The project is still under design, but the foundation is there, hence the publication. If the team has the skills, some projects could benefit from adhering to certain principles of clean architecture, which among other advantages, ensures a high level of maintainability, low coupling, readability, and better adaptability to new technologies. With the help of Anthony Cyrille's training, I started this project to see how to apply clean architecture to a Next JS project. Next JS or React are rarely presented in training courses that choose clean architecture. However, there are many advantages, including the ability to change frameworks without rewriting the entire codebase.

Discover some articles on what is at stake in this project :

Clean architecture (Sánchez Chordi)Programmer Test Principles (Kent Beck)Sur l'architecture modulaire (Ben Slimen)

What I learn :

  • Architecture:
  • Creation of use cases isolated from the React view
  • Use of screaming architecture to name files and folders based on business jargon
  • Modules that correspond to a specific business act, such as 'order' to refer to a table order in a restaurant
  • Dependency inversion is heavily applied: I was able to better understand the D in SOLID by increasing the reusability of code components.
  • Other aspects I learned:
  • I learned to use Redux while I used Zustand much more: another string to my bow.
  • I improved my mastery of TypeScript by learning better rigor.
  • I used gsap to create small animations and tried a navigation mode where it feels like there's no scrolling.