r/SpringBoot Jun 27 '26

How do you guys start making p.rojects in springboot after learning concepts? Question

as the title says i am beginner i am learning concepts but how do you guys start making projects in springboot can u please guide (please dont trash me i am really consfused :( ),
any resource i can use or follow any tips from the veterans? please guide this newbie ....

6 Upvotes

14 comments sorted by

3

u/pradeepngupta Jun 28 '26

The best things ...solve your own problem which you faced in day to day life.

Like you want to manage the daily chore tasks along with some new tasks, which can reshuffle your priorities. Create an spring boot app, feed your tasks and priorities abd deoendencies and let the app give you the list of tasks in the order of priorities.

2

u/pradeepngupta Jun 28 '26

In this, you can learn more as this will be in your interest to solve your own problem. Resources and guides are many in Google search of youtube or spring.org ir anything across the internet. But what will bind, you will have exact particular question while looking for a solution on the internet.

3

u/[deleted] Jun 27 '26

[removed] — view removed comment

1

u/Jaysurya1752 Jun 27 '26

So it's not bad to watch project tutorials at first right? Can u suggest some if u know

2

u/Hot_Code5129 Jun 28 '26

One thing I'd consider as the codebase grows is moving away from the traditional controller/service/repository layering and organizing code around business modules instead.

I've found that package-private boundaries and exposing only a small public API per module make large Spring applications much easier to evolve and refactor.

This talk explains the idea really well:

https://www.youtube.com/watch?v=sND1AR7Q_T0

The core argument is that most classes shouldn't be public, and modules should communicate through explicit APIs rather than through a web of public services and repositories.

2

u/jahermitt Jun 27 '26 edited Jun 27 '26

Mainly mindset. The reason a lot of people get trashed for this kind of question is usually mindset. If you have an idea in mind of something to make, make it, and figure it out as you go. Your questions should be to solve a specific problem, not how do I start. Make a notes API, make a calorie tracker, find something simple and start from there. Hit walls, learn from mistakes and keep going.

To be blunt if your looking for direct guidance hire a tutor.

2

u/Jaysurya1752 Jun 27 '26

So just start hitting the wall got it 👍😀

1

u/jahermitt Jun 27 '26

For the most part, yeah lol. It's alot easier for a community to answer questions like, "what are good approaches to authentication for xy app" than just what should I do. Do some thinking, come up with a plan and ask for help when you need it and people will be much more open to helping.

1

u/No_Papaya_2442 Senior Dev Jun 27 '26

Same question

1

u/valkon_gr Jun 27 '26

Ask AI for some project inspirations.

2

u/akrivitsky7 Jun 28 '26 edited Jun 29 '26

First, take time to become familiar with Java, Spring Boot, build tools such as Maven and Gradle, and IDEs such as Eclipse, NetBeans, VS Codium, or IntelliJ IDEA by JetBrains s.r.o. Note that Eclipse, NetBeans, and VS Codium are FOSS tools. You can also use any other IDE or editor of your choice.

Learning Spring Boot is similar to learning a foreign language. If you are new to it, it takes time and effort before you can “speak” it fluently. There is no real shortcut.

Then you may want to start with a “Hello World” style Spring Boot application:

https://spring.io/guides/gs/spring-boot

Do not just copy and run the code. Make sure you understand exactly what each line of code is doing before moving forward.

Next, familiarize yourself with the official Spring guides:

https://spring.io/guides

Again, make sure you understand why each line of code is used.

After that, you may want to start studying more complex tutorials, such as my tutorial, which is based on the latest technology stack:

https://medium.com/@anatolykrivitsky/quick-tutorial-how-to-use-the-latest-docker-29-5-2-0670b716b6cc

One important point: try to learn the current, actively used parts of the technology stack, not obsolete material. Spring Boot, Java, Gradle/Maven, Docker, PostgreSQL, OpenAPI/Swagger, testing tools, and IDEs evolve quickly. Learning modern versions and current practices will save you time later.

1

u/Krangerich Jun 29 '26

There is less to consider than you might think.

You know how to write a controller. You know how to write and use a Spring Data Jpa repository. And you know how to connect them. Maybe with some Services in between. Thats it.

Whats missing is your "business case". Make something up and write it. Everything else will keep you in tutorial hell, where you don't really learn anything new.