Looking for feedback on a microservices architecture project

[LuizAndradeDev]

🏷️ Discussion Type

Product Feedback

Body

Hey everyone, I built a personal project called Mobflow, inspired by tools like Jira and Trello. The idea was to create something closer to a real SaaS, with multiple Spring Boot microservices, an API Gateway, Kafka, JWT-based authentication, an Angular frontend, and everything running with Docker.

I’d really appreciate honest feedback on the project, especially around the architecture and overall structure. What’s good, what’s not, and what could be improved as a portfolio project. The repository is here: https://github.com/LuizAndradeDev/mobflow

Guidelines

• I have read and understood this category's guidelines before making this post.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[jovbcorreia]

Hi @LuizAndradeDev! Mobflow looks like a really solid portfolio project — the tech choices (Spring Boot microservices, Kafka, JWT, API Gateway, Angular, Docker) are exactly what companies look for in backend candidates. Here's my honest take:

What's strong ✅

• Using Kafka for async communication between services is the right call for a Jira-like tool — event-driven is the correct pattern for notifications, activity logs, etc.
• • JWT at the gateway level is the right architecture — services shouldn't each handle auth independently
• • Docker for the full stack shows you understand real deployment
    What to improve for portfolio impact 🔧

1. Add a docker-compose.yml at the root
Reviewers want to clone and run. If there's no easy way to spin everything up locally, most people won't bother. A single docker-compose up command is a huge plus.

2. Service discovery
If you're not already using something like Eureka or Kubernetes, add it. It's what makes it feel like a real microservices setup vs just multiple Spring Boot apps.

3. README with architecture diagram
Add a diagram (even a simple one from draw.io or Mermaid) showing the services, how they communicate, and the Kafka topics. This is often the first thing a senior engineer looks at in a portfolio project.

4. Centralized logging
Consider adding a basic ELK stack or just structured JSON logging per service. Shows operational maturity.

5. Circuit breaker
Adding Resilience4j for circuit breaking between services shows you understand fault tolerance in distributed systems — a common interview topic.

Overall it's a strong portfolio piece. The architecture is sound — just needs better documentation and a smoother local setup experience. Good luck! 🚀

[heritagefort21]

Cool project using Spring Boot microservices with Kafka and an API Gateway is already solid for a portfolio, especially with Docker setup and JWT auth. If you keep improving observability and service communication patterns, it’ll look even stronger. On a side note, I’ve seen structured breakdown-style feedback communities like this also shared around Fantasy game download, which can be useful for comparing project ideas and approaches.