Great content, Rainer. Thank you! Watching the video, I kept thinking about the locality of behavior and code co-location. From their POV, this "API Spec"-driven development flow rubs me the wrong way. I feel this approach could get messy very fast and I'm not sure if the benefits outweigh the risks. For example, I really admire how you structured your code in the "Application Walkthrough" part and how each action/command got its own service class with the contained "XRequest" record. I believe that's how we usually code - inside out or domain-driven. However, when driven by the "API First" approach, I feel we are now moving "outside in". Let's say you had to extend the last "API First" approach a little bit and implement the Java's add booking feature. Would you then reference the Booking.java of the generated package from inside your "logic" module?
Hello, so I am usually a code-first guy but I know that this approach does not work very well in larger organisations. So when you have multiple teams depending on a particular API, they usually go to API-First.
![[Re:all TREASURE] EP.6 in 방콕ㅣ🚩 쩡캠의 방콕 투어 빵 마이 와이 👍](http://i.ytimg.com/vi/uyFw-nItA_s/mqdefault.jpg)
Another fantastic content. Awesome. Looking forward to see Spring OAuth + OpenID + Spring Session integration with SPA frontend. Thanks a lot.
Yup, that was the idea. The article has already been published several months go. The video is missing.
@RainerHahnekamp lovely, ur contents are fantastic. Please keep them coming in. 🙏🙏
Absolutely amazing Content Rainer! Thanks much
You are very welcome Robert.
Great content, Rainer. Thank you!
Watching the video, I kept thinking about the locality of behavior and code co-location. From their POV, this "API Spec"-driven development flow rubs me the wrong way. I feel this approach could get messy very fast and I'm not sure if the benefits outweigh the risks.
For example, I really admire how you structured your code in the "Application Walkthrough" part and how each action/command got its own service class with the contained "XRequest" record. I believe that's how we usually code - inside out or domain-driven. However, when driven by the "API First" approach, I feel we are now moving "outside in".
Let's say you had to extend the last "API First" approach a little bit and implement the Java's add booking feature. Would you then reference the Booking.java of the generated package from inside your "logic" module?
Hello, so I am usually a code-first guy but I know that this approach does not work very well in larger organisations. So when you have multiple teams depending on a particular API, they usually go to API-First.
And thanks for pointing out the "Application Walkthrough"!
How can I download this code.. any chance
Yes, please try that one and let me know if you have any questions: github.com/rainerhahnekamp/spring-angular-openapi