OpenAPI with Spring & Angular

Рет қаралды 1,700

Күн бұрын

In this video, I explain how to use the OpenAPI for type-safe communication between Spring and Angular.
I will also do an application walkthrough, where I explain a minimal Spring application, which uses the latest features of Spring Boot 3 (for example Testcontainers).
The GitHub repository is available at github.com/rainerhahnekamp/sp...
0:00 Introduction
1:14 Theory
6:53 Application Walkthrough
16:00 "Code First" Approach
30:40 Upload via OpenAPI
36:07 "API First" Approach
49:43 Summary

Пікірлер: 10

@DJpiya1 2 күн бұрын

Another fantastic content. Awesome. Looking forward to see Spring OAuth + OpenID + Spring Session integration with SPA frontend. Thanks a lot.

@RainerHahnekamp Күн бұрын

Yup, that was the idea. The article has already been published several months go. The video is missing.

@DJpiya1 Күн бұрын

@RainerHahnekamp lovely, ur contents are fantastic. Please keep them coming in. 🙏🙏

@robertkameni5975 7 ай бұрын

Absolutely amazing Content Rainer! Thanks much

@RainerHahnekamp 7 ай бұрын

You are very welcome Robert.

@indrek843 8 ай бұрын

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?

@RainerHahnekamp 8 ай бұрын

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.

@RainerHahnekamp 8 ай бұрын

And thanks for pointing out the "Application Walkthrough"!