Hi Josh! I understand that this is just another way to do it, but what advantages or disadvantages do you find in going with DSL vs regular annotation-based controllers? Maybe there is some objective benefits in some situations? And another question: why would somebody switch from annotation-based controllers to such handlers? Thanks in advance!
i covered all of these things in the video, but for posterity: - it's not either/or. you can use both the functional reactive style and annotations in the same app - you might use the DSL if u want more control over request matching or when / if handlers are registered than you might get using `@RequestMapping` + methods. - you might use controllers if you like the more natural expression of controllers as collocated handler methods sharing similar dependencies.You might also use them since that's what most of us have always used. No need to change if you're happy ;-)
@@coffeesoftware The disadvantages i see with this approach from now is not have automatic bean validation, there are others like swagger integration, however, for me this is the only one directly related with spring. Any one knows when this feature will be able to use?
@@coffeesoftware thanks. What I mean is that teams usually decide on patterns thay would follow. If there's another way to do something, you don't just start using it for the sake of trying, you need some objective advantage in specific situations.
Hi Josh! Can you please create a blog post or a video on how to structure a project using hexagonal architecture at the same time using spring functional approach? youtube.com/@coffeesoftware
This is awesome, thanks for sharing this video...
Thanks josh sharing such a kind of perfect videos using ur time.Please move on.
Hi Josh! I understand that this is just another way to do it, but what advantages or disadvantages do you find in going with DSL vs regular annotation-based controllers? Maybe there is some objective benefits in some situations? And another question: why would somebody switch from annotation-based controllers to such handlers? Thanks in advance!
i covered all of these things in the video, but for posterity:
- it's not either/or. you can use both the functional reactive style and annotations in the same app
- you might use the DSL if u want more control over request matching or when / if handlers are registered than you might get using `@RequestMapping` + methods.
- you might use controllers if you like the more natural expression of controllers as collocated handler methods sharing similar dependencies.You might also use them since that's what most of us have always used. No need to change if you're happy ;-)
@@coffeesoftware The disadvantages i see with this approach from now is not have automatic bean validation, there are others like swagger integration, however, for me this is the only one directly related with spring. Any one knows when this feature will be able to use?
@@coffeesoftware thanks. What I mean is that teams usually decide on patterns thay would follow. If there's another way to do something, you don't just start using it for the sake of trying, you need some objective advantage in specific situations.
OMFG! Perl web framework?! Is it you? Long time no see. Nice to meet you.
19:50 with Lombok you can use @RequiredArgsConstructor
how would you reuse handler programmed for webflux returning Mono (server reponse from reactive package) to be configured using webmvc.fn ?
Nice.
Other than having all routings in one place, is there any other benefit to this approach?
Hi Josh! Can you please create a blog post or a video on how to structure a project using hexagonal architecture at the same time using spring functional approach?
youtube.com/@coffeesoftware