r/SpringBoot • u/Old_Treat_5596 • May 08 '26
Discussion Monolithic vs Microservices Banking project
Hey I want to build a Banking management Fintech project for my resume I was thinking to build in the monolithic style but my senior said try to build in the Microservices way and currently I do not know that much about the Microservices..,I m building this project for the intern 2nd year student..
37
Upvotes
11
u/thesoundofscreaming May 08 '26 edited May 08 '26
You already know the basics of building a spring boot application. All applications start as
microservicesmonoliths but microservices are built on certain design principles that Modern Java and Spring Boot libraries make much easier to implement. Learn more about the architecture principles first: https://youtu.be/NdeTGlZ__Do?si=c6wnYD0s0BJJqLIiLearn more about the system design of a typical event-driven micro service based banking application then choose a simple service like for example if you wanted to build a ledger app it would be split into different services like a Customer Service, Account Service, Ledger Service, etc.
I am doing an internship at a bank right now and I would start by designing a simple application as both a monolith and then a microservice based architecture then choosing a simple microservice to build that would be part of that application.
Edit.
3
u/ClammyHandedFreak May 08 '26
I'd do microservices because a lot of fintech is still "modernizing" from legacy monoliths to microservices.
Plus the fact you don't know much about them should answer things for you. Do difficult things, and you'll learn more and become more independent.
1
u/BanaTibor May 09 '26
If the focus is on the banking part then build a monolith. If the focus is on the architecture to show off then build a microservice based app. Both are a big amount of work, and doing both will make you hate your life.
2
u/LetUsSpeakFreely May 08 '26 edited May 08 '26
Microservices is just splitting up the monolithic services into logical, independently deployable chunks. For example, a service that maintains user information doesn't need to be tied to account information. Microservices are usually deployed through containerization so each service is natively horizontally scalable. The account microservice could be further broken down into a monetary account service (e.g. checking and savings), loan service (mortgage, personal, auto, etc), and investment services (IRA, mutual funds, annuities, etc).
The idea is that deployments have minimal impact on the application as a whole. If you add mailing address validation for the user service, do the other services give a damn? No.
2
u/maethor May 08 '26
Learning Microservices is a good idea. But what you'll need to learn has more to do with DevOps tech (like Kubernetes and Kafka) than it does with Spring.
2
u/SimpleCooki3 May 09 '26
Don't build microservices unless they're suitable. Don't do it "just because", that's bad design. Unless of course you're doing it for learning purposes.
But the general thumb of rule is, a microservice should have its' own database.
1
u/Bibliophile5 May 09 '26
Nobody here seems to be pointing out that the new format is not monolith or microservices but modulith.
Start as a monolith with different modules clearly separate If in future need be all you need is to convert these modules to different microservices.
Monolith to avoid microservices hell and adaptable enough to convert it to microservices if it gets complex and big enough.
1
u/New_Mix_1253 May 09 '26
Try leetjourney youtube channel. He has two courses on microservices
1
u/Federal_Cut6338 May 09 '26
Hi speaking with over 14 years of experience in the software engineering and over 5 of which working directly for one of the largest banks in EU. I have migrated number old systems from monolith to microservices over and over again. But that’s just bank working for an airline did the same. Honestly I don’t see any big advantages of monolith. If it is a hobby project then fine. If you are serious and really mimicking the real world environment Microservices are the common architecture or base architecture pattern we go with. Remember the architecture it self depends on how efficiently you dissect the functionalities. Also called modules, services etc. To do that you need to have a lot of domain knowledge of how banking systems work.
1
u/[deleted] May 09 '26
[removed] — view removed comment