You missed the whole point of Spring boot.
It's not mvc + persistency.
This is about auto-configuration of almost each and every existing technology /stack. From simple rest service with embedded tomcat or netty to the complex application (messaging middleware, scheduling, retry, load balancing, caching, service registration and discovery, various communication layers, logging.. Should I continue?
I stopped reading after this paragraph :
Spring Boot Architecture has four layers:
Presentation Layer
Business Layer
Persistence Layer
Database Layer
You missed the whole idea of Spring boot !!!
Thank you for your comment. What did I miss, precisely?
You missed the whole point of Spring boot.
It's not mvc + persistency.
This is about auto-configuration of almost each and every existing technology /stack. From simple rest service with embedded tomcat or netty to the complex application (messaging middleware, scheduling, retry, load balancing, caching, service registration and discovery, various communication layers, logging.. Should I continue?
Sure, you are more than welcome to continue. 😁
I agree with your comment, and I'm fully aware that there is more than just "mvc + persistency".
For this article, I chose to focus on giving an overall understanding of the Spring Boot Architecture.
I blog frequently and I'll cover more Spring Boot topics in my next articles (this is my very first article about Spring Boot).
Also, let's not forget that in software engineering you don't need to know everything, but just enough to get you going.
We start small and we learn more as we go. 😊
overall understanding of the Spring Boot Architectureis about files namedspring.factories. No more nor less.Thanks @jvmlet 😁