Full Stack Reactive with React and Spring WebFlux

No video

Full Stack Reactive with React and Spring WebFlux

Рет қаралды 55,706

Күн бұрын

You have streaming data and want to expose it as reactive streams with Spring Boot. Great! Spring WebFlux makes that pretty easy. But what about the UI? Can you stream that data to the UI and have it be reactive and constantly updating too? This session explores techniques for making your app fully reactive with Spring WebFlux and React. Mostly live coding, with plenty of time for Q & A in the midst of it all
Speakers:
Matt Raible
Developer Advocate, Okta
Filmed at SpringOne Platform 2018

Пікірлер: 21

@trozzonick77 4 жыл бұрын

Cool lad , met him in Birstol, crazy knowledge

@Ashabrol 3 жыл бұрын

How are the classes getting generated automatically using the web flux commands? Is there a library that needs to be added in pom.xml?

@g1patil 3 жыл бұрын

Template. You can assign whole code to custom command in IntelliJ .

@tungnguyenuc7223 2 жыл бұрын

I have question . In case if all message broadcast through webSocket if i want this message for specifically user . How can i do . Any people help me

@erorci 5 жыл бұрын

What is necessary to configure in order to use webflux-entity shortcut?

@mraible 5 жыл бұрын

I used IntelliJ IDEA's Live Templates for this feature. You can find the ones I use in my demo's, including webflux-entity at github.com/mraible/idea-live-templates.

@luongnguyen895 4 жыл бұрын

@@mraible thanks so much. Any shortcut free u can share at?

@PeterSotosEPT 5 жыл бұрын

Matt is there a Github Repo for this code?

@tanveerhasan2382 3 жыл бұрын

I guess not

@alexkaidoomicah3828 5 жыл бұрын

which library does the http command belong to?

@canyonke 5 жыл бұрын

HTTPie

@krige 3 жыл бұрын

Can anyone understand what he says at 9:28: "this is a great way to implement something that is not recommended on _?_ radar"

@krige 3 жыл бұрын

thoughtworks!

@10xtenx10xtenx10xten 2 ай бұрын

3 years late, but what he's saying is that your ORM object shouldn't be the same object on the response payload. Because it exposes what your data schema is like. It also ties your contract and db schema. For example if you want return a field called id to the client, but in the future you want to return itemId or something. You would have to also do it on the database side.