Spring Boot V/S Vert.x

S. No	Parameters	Vert.x	Spring boot
1	Primary Focus	Vert.x is designed to build your large-scale, super-scalable and distributable web applications which might have less complex business logic in them, but need to perform reliably under massive load.	SpringMVC is focused on enterprise processes and enterprise applications with lower user counts.
2	Reactive Manifesto 1. Asynchronous messaging 3. Elastic 4. Resilient 5. Responsive	Vert.x is reactive. Vert.x uses asynchronous messaging, a mechanism that scales. It is particularly useful in mircoservices because messages do not care whether you send them across the network or locally in the same JVM.	Spring is not reactive. Spring does not support asynchronous messaging.
3	Non-blocking, event driven runtime	Vert.x provides a non-blocking, event-driven runtime	Spring causes blocking i.e. waiting a task can block the process to a deadlock stage.
4	Lightweight/Heavyweight	Vertx is more like a toolkit, very raw and down to the bone. That makes it very flexible because it allows you to tailor and tune the application according to your needs.	Spring is opinionated and heavyweight
5	Performance	Recommended	Less compare to Vert.x
6	Online support	Less as compared to Spring	Springs ecosystem is huge and it's easier to find help online:
7	Testing & Debugging	Testing and debugging is not as straightforward as testing traditional, synchronous, blocking code.	Spring on the other hand makes it easy to test your code.
8	Managing shared resources	Easier to manage shared resources whether synchronization or parallel processing	For shared resources, Spring causes problem in synchronization & parallel processing.
9	Concurrency and Scalability	A Vert.x application consists of loosely coupled components, which can be rearranged to match increasing performance requirements	Less compare to Vert.x
10	Polyglot	Vert.x is polyglot. Applications can be written in several languages viz. Java, Python, Groovy, Ruby, and JavaScript	Spring allows Java only