Great presentation! Jimmy mentions on 59:00, that they've built a "Unit of work" for a data storage that does not support it out of the box. Are there any examples available online?
I've discovered the same architecture, in the same way you did. And, by experience, do not reuse code between handlers. There is nothing wrong on having copied/pasted code. Keep in mind modifications will come per feature, so, probably, this code will need to evolve independently, and the duplicated code will not be duplicated any more.
This architecture has been around for over 20 years in the modular monolith/modular client. What this video really shows is how little most developers really understand about software architecture and how poorly it seems to have been taught for a long time.
He didn't invent VSA. He formalized it. VSA is described in the Clean Architecture book by that old guy, uncle Bob or something like that. 😅 Joke aside I don't know for sure if it's even older than that or who's described the idea first.
man OOP makes this stuff so overcomplicated this entire architecture just looks like a request handler function anyone that has any experience with express.js for instance has already been using this architecture.
Just avoid layers. Simple as that. The result of you instead localizing your code around subjects will end up in about this architecture. The name is bad as it could suggest you should stick with the layers.
Great presentation! Jimmy mentions on 59:00, that they've built a "Unit of work" for a data storage that does not support it out of the box. Are there any examples available online?
I've discovered the same architecture, in the same way you did. And, by experience, do not reuse code between handlers. There is nothing wrong on having copied/pasted code. Keep in mind modifications will come per feature, so, probably, this code will need to evolve independently, and the duplicated code will not be duplicated any more.
This architecture has been around for over 20 years in the modular monolith/modular client. What this video really shows is how little most developers really understand about software architecture and how poorly it seems to have been taught for a long time.
Agree and then populating all medias with good clean architecture courses :) I feel same aspect Divide and Conquer only different context.
I used already Vertical Slice architecture at the beginning of my career, it was then known as Big Ball of Mud
Can not agree more😅😅😅
The biggest advantages of using vertical slice architecture is FEWER MERGE CONFLICTS!
He didn't invent VSA. He formalized it. VSA is described in the Clean Architecture book by that old guy, uncle Bob or something like that. 😅
Joke aside I don't know for sure if it's even older than that or who's described the idea first.
man OOP makes this stuff so overcomplicated
this entire architecture just looks like a request handler function
anyone that has any experience with express.js for instance has already been using this architecture.
Just avoid layers. Simple as that. The result of you instead localizing your code around subjects will end up in about this architecture. The name is bad as it could suggest you should stick with the layers.