Building a Secure Banking Application with Java and Spring Boot: Complete Tutorial - Part 2

Learn how to build a secure and functional banking application from scratch using Java and Spring Boot in this comprehensive tutorial. Whether you're a beginner or an experienced developer, this step-by-step guide will take you through the entire process of designing, developing, and deploying a robust banking application.

Throughout the video, we'll cover essential concepts and techniques, including user authentication, transaction management, account balances, and more. By leveraging the power of Java and Spring Boot, you'll gain insights into building scalable and maintainable banking applications.

Key topics covered in this tutorial include:

Setting up a Java development environment and installing Spring Boot
Designing the database schema for banking-related entities
Implementing user authentication and authorization using Spring Security
Building RESTful APIs for managing accounts, transactions, and balances
Integrating data validation and error handling mechanisms
Enhancing security measures with encryption and secure coding practices
Deploying the banking application to a web server
By the end of this tutorial, you'll have the knowledge and practical skills necessary to create your own banking application using Java and Spring Boot. Join us on this coding journey and start building your banking app today!

[uyinokuta]

Weldone sir, I really love your video. I have some questions though. I'm also trying to create a Banking Application and your video is a great guide for me as a learner. In my Model package, I have Customer, Account, Staff, and Transaction. I also have BVN as part of the required fields in my Customer class but I was thinking, what if the customer doesn't have a BVN? My application should be able to generate a Unique BVN and and checks that, that BVN does not exist in my database. So the BVN will be a required field but if it doesn't exist, a BVN will be generated and given to the customer which the customer can use to open several other accounts. Please how can I implement that logic in my service layer?

[osikisegun]

Great tutorial and it works, just subscribed to your channel. when should we be expecting the follow up tutorial?

[aududaniels]

Thank you so much boss! quite interesting and comprehensive

[victorcousin]

U got a new subscriber... Thanks for ur great explanation and simplification.

[lakshaychaudhary]

sir can you please share the link of github repo, from where i can take help to build this ?

[surya]

in accountBalance u took
BigDecimal i never seen till now generally we will take Double or Float what is the Special about BigDecimal ?

[thangtrinh]

Thank you for sharing. Can u share your Github repository for this source code?

[godwingodfrey]

Thank you so much for this, the tutorial is very clear and straightforward .

[sujitkumar]

Awesome 👍 can you please share a source it would be very helpful.

[thompsonidowu]

Thank you so much brother. You are the best

[uyinokuta]

So i created an AccountModel class because i believe a customer can have multiple accounts of different Types and varieties of transaction.

[lakeman]

Great work chief. I had an error from the application properties, I had to add spring.jpa.database=mysql to the properties file. You should consider adding it.

[surya]

while generating the project u selected packaging as jar .if we select packaging as jar we cannot deploy in external servers right? so i think it is better to select war so that we can deploy in external serves and we can even use embeded tomcat server which comes by default right correct me if i am wrong and it is better to add dev tools also right so that it can reconize the changes automatically

[surya]

Please don't mind i am getting so many doubts this is the first application I am building after completion of my spring boot course



In the entity Class u have all the fields and useRequest class u have same fields which are three in the entity class ..I understand that u created dto class as useRequest because u want to expose only necessary fields to the end user but why writing properties in both classes we can use Compostion right ? And if we do like that we can even set the details of User request obj to User class has a property using beanUtils.copy method instead of writing more lines in create User method ..pl correct me if I am missing anything

[olanrewajusaka]

Good work bro...Just want to ask a question sir, does this how the real world banking application works like the ones our N
igerian banks uses.. is it the real world app

[Repeooo]

Dear sir, please give me github link repo so i can follow coding method easily.

[Star_Academy-dwin]

Hi sir @thejavaacademy-18, where we can see the source code of this proyect?

[surya]

i would like to add validations for email and controlling size of the name filed. and instead of taking mobile number as String i would like to use Long

[emmanuelahola]

Great work boss, can i get the code from your repo and follow along

[cristimanolache]

Why did you create user using Builder?

I think you can use User user = new User().

What is the difference?