...
| draw.io Diagram |
|---|
| border | true |
|---|
| |
|---|
| diagramName | CPS-821 |
|---|
| simpleViewer | false |
|---|
| width | 1000 |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| diagramDisplayName | Proposed Design |
|---|
| lbox | true |
|---|
| diagramWidth | 1181 |
|---|
| revision | 1619 |
|---|
|
High-level Steps/Possible Tickets:
...
Source: https://docs.spring.io/spring-framework/docs/current/reference/html/web-reactive.html
Pros & cons
| Pros | Cons |
|---|
- Better scalability due to non blocking threads
- Use less threads (1 per core)
- Better CPU Efficiency
| Reactive web programming is great for applications that have streaming data, and clients that consume it and stream it to their users. It ain’t great for developing CRUD apps. If you want to develop a CRUD API, stick with Spring MVC. - Steep learning curve in the shift to non-blocking, functional, and declarative programming
|
Links to materials:
https://www.baeldung.com/spring-webflux
...
