Normally we are comparing the Solon ecosystem with the SpringBoot ecosystem.Instead of Solon-Boot (which is a functional module only) with the SpringBoot ecosystem, but both names are too misleading.
Solon-Boot
Solon-Boot represents only the "server-side" bootstrap of Solon (equivalent to the Solon server bootstrap). It is a "functional" module partitioning concept, comparable to Solon-Data, Solon-Net, and Solon-Serialization. For example:
- solon-boot-jdkhttp, meaning boot jdkhttp
- solon-boot-smarthttp, meaning start smarthttp
- solon-boot-jetty, meaning boot jetty
- solon-boot-websocket, meaning boot websocket
- solon-boot-socketd, meaning boot socketd
SpringBoot
SpringBoot is different. It represents a bootstrap (equivalent to Spring bootstrap) that makes Spring easier to use. It is a concept of architectural hierarchy evolution, which is equivalent to taking Spring up a level. Using Spring directly will be more troublesome. (from web search)