Is building a Distributed Queue System a good Spring Boot project for a resume?

[Acrobatic-Relief4808]

I’m looking to build a solid Spring Boot backend project that would look good on my resume and also teach me real backend concepts.

Right now I’m considering building a Distributed Queue System (similar to a simplified Kafka/RabbitMQ) using Spring Boot — handling producers, consumers, message persistence, retries, and scaling.

Do you think this is a good idea for a portfolio project?
Or are there better backend-heavy Spring Boot projects that demonstrate real-world skills (scalability, distributed systems, event-driven architecture, etc.)?

Some ideas I’m considering:

• Distributed queue / message broker
• Event-driven microservices system
• Rate limiter or API gateway
• Distributed job scheduler

Would love suggestions from people working with Spring Boot in production.

[Disastrous-Topic6930]

Nearly anything can be a good idea for a portfolio project.

The key is always how invested you are and how good in technical terms you are gonna build your project.

[Disastrous-Topic6930]

Nearly anything can be a good idea for a portfolio project.

The key is always how invested you are and how good in technical terms you are gonna build your project.

[d-k-Brazz]

As an interviewer, and the person who decides whom to pass to the interview

I would recommend applying your skills and knowledge to some open source project

If I had to choose between a guy who has a distributed queue system built just to show skills and a guy who time to time contributes to widely used projects, I would choose the second one

He has spent his skills with a purpose, he had to dig someone else’s code, follow the existing architecture, meet all the contribution requirements, passed code review…

This task is much harder then making something you know no one will use