Atlanta - Reactive Spring

[@daddashikamani]

Perfect! So the UI call the edge service which calls the microservice. It'll create an active http connection which is non-blocking. Does this mean we don't need scaling of services? How does it impact code which has been written to be hosted on cloud? Do we need less instances to service the same number of requests? Can somebody provide the numbers?

[@adityakhajuria7642]

where I can find the slides ?

[@patrickproctor3462]

I really, really wish the Start.Spring.io team would implement a project builder that let you opt out of Spring Boot itself. I've seen and fixed too many instances of dependency collision and stomping. Because Boot tries so hard to manage it and work in tandem with the shaded components, it all goes unnoticed until someone changes the order of some bean construction. At which point, it turns out there was a mess of Log4J, SLF4J, Logback, SLF4J over Log4J, and Log4J over SLF4J lurking under the surface, and it's now got stack overflows 8 ways from Sunday because the Jenga Tower finally fell. Just, no. Give me a raw Spring 5 project that sets up a single rest endpoint from void main(...) with a functional bean initializer and a direct construction of the web server with port 8080, and make the call stack obvious. And let me "Fail Fast" when I drag in libraries and dependencies from 3rd parties. And let the team of junior devs doing POC buildouts fail fast! Stop trying to keep enterprise people from solving real problems early! And stop burying the Spring Framework docs and API spec deeper and deeper into the project site!

[@valeenoi2284]

I pretend I understood everything you said.