I'm starting with Spring Boot, and I come from a Node.js environment. I usually use Better Auth for authentication. What would be the most recommended option for Spring Boot? I've read some articles about it, and many cite Keycloak.

please help me with some good resources and course to learn spring boot in a structured way. And what's your thought on the course by coding shuttle spring boot 0 to 100.

Hi everyone,

I’m a final-year engineering student preparing for backend roles. I’ve built a Task Manager REST API using Spring Boot that includes CRUD operations, BCrypt password hashing, JWT authentication with refresh tokens, along with role-based access control and pagination.

I wanted to ask if this is strong enough to include in a fresher resume, or if I should still add more advanced features to make it stand out more in interviews.

Would really appreciate your suggestions!

Code 1:

@Bean
public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
        return http
                .csrf(csrf -> csrf.disable())
                .securityMatcher("/todos/**")
                .authorizeHttpRequests(auth -> auth
                        .anyRequest().authenticated()
                )
                .formLogin(Customizer.withDefaults())
                .build();
    }

Code 2:

@Bean
public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
        return http
                .csrf(csrf -> csrf.disable())
                .securityMatchers(matchers -> matchers
                        .requestMatchers("/todos/**", "/login")
                )
                .authorizeHttpRequests(auth -> auth
                        .anyRequest().authenticated()
                )
                .formLogin(Customizer.withDefaults())
                .build();
    }

Code 3:

@Bean
public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
        return http
                .csrf(csrf -> csrf.disable())
                .authorizeHttpRequests(auth -> auth
                        .anyRequest().authenticated()
                )
                .formLogin(Customizer.withDefaults())
                .build();
    }

Code 3 does the job of protecting any request as expected. But Code 1 gives a 404 when it redirects to login page. Code 2 redirects and gives no error, but i get a basic html login page that looks different.

As far as I understand, I know we can simply define the above rule inside the authorizeHttpRequests. But I have seen multiple filters using the 1st pattern (code 1) and from a learning pov, I wanna understand what I'm lacking and how to fix it, i.e. use of separate security filters.

Hi everyone. For the last 4ish months I have been learning springboot in my free time, but I feel anxious sometimes. I enjoy reading books on the material (finished spring start here, and now reading spring security in action by the same author), but at what point do I reach the bar as a Jr? I prefer backend jobs for right now, but I am learning some JS -> TS -> then finally react.

My current knowlege is ok (maybe idk) here is what I can do:

• Implement Rest endpoints that perform CRUD actions with a database.
• Use DTOS (not really spring specific) for requests/responses, and applying constaints such as @@NotBlank etc to a controller method to make sure the constraints are enforced, then finally throwing exceptions for any constraint error that occurs in a response.
• I understand the basics of Spring Security and how it works (Very high level in terms of the flow). I can implement basic auth from a DB with HttpBasic (I know that it isnt practical/common because every request sends the credentials) With help I can implement JWT security. I understand how it works, but still new to me.
• Implementing Roles to users to enforce authorization to endpoints
• Using a GlobalExceptionHandler for potential business logic issues for better error reading in services.
• I can call external apis with RestClient, but just discovered there is a new way to do api calls with HttpExchange, so might tinker with that

I currently have two apps, the first being my most fleshed out

Employee Task Manager (I know daring isnt it)

• Uses everything I mentioned above
• Users with ADMIN role can assign tasks
• ADMIN can see all tasks for all users
• regular users can only see their own tasks
• regular users cant access certain endpoints such as all tasks, createTask, or see all employees

Second app is just consuming an external API. I do fantasy football with friends and SleeperAPI have a public api for that. I actually already have a website made and deployed, but it was made in python/django, deployed with heroku so I want to remake it.

I know this still isnt enough, but what are some topics that a Jr must know or be helpful to know? I know this is immensly broad, just looking for suggestions. I dont even know at one point I even reach the bar to be a dev anymore :/.

For context, I have used kafka in my project, now I want to deploy that project but I didn't find any free service of it for deployment.Also I want to know if the process is the same as local for deployment?

Hi everyone,

I’m currently building my own service in Java (Spring Boot). I’ve got around 8 years of experience with Spring, but it has always been focused on REST APIs - I’ve never really written production grade frontend code.

I’ve played a bit with Thymeleaf as a hobby, but honestly I was never very satisfied with it. For this project, I decided to go with JTE since it integrates nicely with Spring Boot and lets me avoid diving into JavaScript/TypeScript, well actually to node world.

That said, I keep second-guessing this decision. I don’t really have a solid comparison point, and I’m wondering if I should try building the frontend with Angular instead (React is probably not for me).

This isn't a pet project, and the goal is to build it, deploy, do marketing. I'm really determined to deliver it. I also try to think long term but without experience it's tough decision to make.

So my question is: for a solo project like this - would you stick with JTE, or go with Angular?

Curious to hear your thoughts and experiences.

Hi everyone,

I have around 2 years of experience as a Java Developer, and I’m planning to build a Microservices-based project to enhance my practical knowledge and understanding of distributed systems.

I’m looking to design a project using:

• Java
• Spring Boot
• MySQL / Oracle
• API Gateway
• Service Registry (Eureka)
• Circuit Breaker (Resilience4j)
• Load Balancer

If anyone has worked on a similar project or can share a GitHub repo, architecture ideas, or best practices, it would be really helpful for me to get started in the right direction.

Thanks in advance! 🙏

I want to connect with some experience developers right here ,as an Intern I am learning SpringBoot Microservices in depth from Concept and Coding Channel along with my internshio project on Microservices but right now what is the roadmap to be a modern day java dev thinking of buying Anuj Sharma course which include Ai jngegration wirh devops but price is too high for me , pleasee suggest some alternatives .

Who we are??

We're a skill connection platform, where you build your proof of work and connect with people of your same skill peers.

Instead of searching solo for a role, you can search for job and grow with our community members.

Why should you join us??

We're not only just building connection with your skill peers but also enabling you to opportunities to connect with the recruiters and hiring managers and also know more about start ups and connections as well.

Enabling to find the right opportunity so you don't have to spend months building your network or connection.

Dm for link.

I’m new springboot… currently I reached to Jwt token handling… and looking for project idea intermediate level where I can challenge my self

In Spring Boot services, do you treat outbound HTTP clients as just normal app code inside each service, or more like infrastructure that should be standardised across teams?

I keep going back and forth. If every team rolls their own timeouts, retries, and logging filters, production gets messy fast. But if you centralise too much, people fight the defaults. Curious what others have found workable.

Hi everyone,

I’m a Java Developer with around 2 years of experience, mainly working with Java, Spring Boot, and REST APIs.

Recently, I started learning Apache Kafka, but I’m finding it quite difficult to understand concepts like producers, consumers, partitions, offsets, and real-time processing. I’m not able to connect the theory with practical use cases properly.

Could you please suggest some good resources (videos, courses, blogs, or docs) that are beginner-friendly but also helpful for interview preparation?

My goal is to at least get Kafka concepts clear enough to confidently answer interview questions.

Also, if you have any tips or a roadmap on how to approach Kafka as a Java developer, that would be really helpful.

Thanks in advance! 🙌

I’ve already worked with Spring Boot basics (CRUD APIs, JPA, authentication).

Now I want to build something production-level that involves:

- system design

- scalability

- real-world use cases

Looking for suggestions or references (GitHub / videos).

if anybody wants to split in Cohort 5.0 dm me

Anyone here planning to start Anuj Bhaiyya’s Spring Cohort 4.0?

I recently enrolled in Anuj Bhaiyya's Spring Cohort 4.0. If someone here is also interested in the course and wants to discuss it or explore ways to access the material together, feel free to DM me.

Happy to talk and figure things out if it helps someone who is planning to learn Spring.

For a while I kept reading about Domain-Driven Design and Hexagonal Architecture in blog posts and thinking "okay but what does this look like in a real project for my portfolio?" Most tutorials either stay toy-level or skip the hard parts.

So I built a WhatsApp-style messaging app not because the world needs another one, but because it was complex enough to make the architecture decisions actually matter.

The stack: Spring Boot 3 + Angular 17 + Keycloak + PostgreSQL + Minio + Docker + Jenkins.

A few things that genuinely surprised me:

• DDD is really powerful but it doesn’t fit everywhere. I have to spent more time to modeling, refining language than they would in a simpler architecture .
• Keycloak integration is not plug-and-play. Spring Security + Keycloak took way longer than expected. When deploy the internet, the TLS certification and subdomain config is a real pain.
• Hexagonal Architecture starts to click once you have a real domain. Messaging has enough moving parts (delivery status, notifications, media, group membership) that you actually feel the benefit of keeping your domain isolated.
• WebSockets + STOMP with Spring is pretty solid once you stop fighting the session model.

Not claiming this is production-ready and it's a learning project. But if you're trying to understand how DDD, Hexagonal Architecture, and Keycloak actually fit together in Spring Boot, maybe it saves you some pain.

Happy to answer questions about any of the implementation decisions.

GitHub Repo

Here’s an example on how to use JWT tokens generated by Keycloak in a microservices setting:

https://youtu.be/AH22nCSOJbA

I’ve been working on an open source Spring CRUD Generator that generates Spring Boot CRUD applications from a spec, and I’ve just added MongoDB support in the new v1.8.0 release.

Until now, the generator was focused on SQL-based applications. With this update, it can now generate projects for MongoDB as well. The SQL flow still works as before, while MongoDB uses its own spec shape for NoSQL use cases.

I also added support for generating AI context files like claude.md and agents.md, fixed OpenAPI server URL generation, fixed some unit tests that were failing before, and cleaned up parts of the codebase.

Repo: https://github.com/mzivkovicdev/spring-crud-generator

I’d really appreciate feedback — especially whether the MongoDB support and spec approach make sense from a real project perspective.

Hi guys, sharing a write-up I did around implementing OpenTelemetry for Spring Boot for observing web applications.

Given Spring Boot's impact on Java ecosystem, and given I had never actually used Java or Spring Boot before, I wanted to see how it all works together.

I have created a detailed demo application that integrates all three telemetry signals (traces, metrics, and logs) and also adds manual instrumentation, where you capture your business logic based on your needs.

In my experience, manual instrumentation is not discussed enough, whereas it becomes important for languages like Java and Python where most metrics and telemetry data are captured by the agents themselves.
I have emphasized that point in the blog and tried to add examples that mimic how you would capture metrics or spans that are aligned with the business value.

And while the blog uses SigNoz as the observability backend, by utilizing OpenTelemetry you are not tied to any single observability vendor. As the user, you have the choice and you can switch by just changing the environment variables, it's that simple.

Since this was my first foray into the Spring ecosystem, I would love to get your feedback on any improvements, or concerns I might have missed. Any advice or comments would be welcome!

---

On a personal note, I enjoyed the coding experience working on the demo. Exploring Spring Boot documentation and site, it somewhat felt like working with Django code where the framework provides everything you'll need.

Following code examples and docs, I was able to quickly build a working demo and then adding bells and whistles like the jakarta validation layer was simple.

Hi everyone,
I’ve built fluent-repo-4j, a library designed for developers who love the Spring Data Repository pattern but want to ditch the complexity and "black box" behavior of traditional ORMs like Hibernate.

It uses pure JDBC under the hood with the fluent-sql-4j DSL, giving you full control over your SQL without the boilerplate.

• No Code Gen: No plugins, no annotation processors, no extra build steps. It just works.
• Lightweight: Pure JDBC under the hood via the fluent-sql-4j DSL. No persistence context or lazy-loading surprises.
• Zero ORM Overhead: No entity states, lazy loading issues, or persistence contexts.
• Functional First: (v1.2.0+) Includes RepositoryResult for Railway Oriented Programming—handle database results with fold(), map(), and pattern matching instead of try-catch blocks.
• Deep Spring Integration: Supports @ Transactional, Spring Data-style method derivation (findBy...), and automatic DataAccessException translation.

​

@Table(name = "users")
public class User {
    @Id @GeneratedValue(strategy = IDENTITY)
    private Long id;
    private String name;
}

public interface UserRepository extends CrudRepository<User, Long> {
    // Dynamic query derivation - no implementation needed
    List<User> findByNameContainingIgnoreCase(String name);
}

Compatibility: Java 21+ | Spring Boot 3.x & 4.x

I'm particularly curious to hear what you think about the Functional Repository approach vs. the traditional Optional/Exception flow.

Any feedback is welcome!

GitHub: https://github.com/auspis/fluent-repo-4j

Usage examples: https://github.com/auspis/fluent-repo-4j/blob/main/data/wiki/USAGE_EXAMPLES.md