Java-Spring-CRQS-Eventsourcing-Microservice VS sagan

Source code you can find in GitHub repository The main idea of this project is the implementation of Event Sourcing and CQRS using Java, Spring and EventStore using Postgresql, previously have written same article where implemented the same using Go and EventStoreDB, think EventStoreDB is the best choice for event sourcing, but in real life at some projects we usually have business restrictions and for example usage of the EventStoreDB can be not allowed, in this case think postgres and kafka is good alternative for implementing our own event store. Didn't write in this article about Event Sourcing and CQRS patterns,th e best place to read is microservices.io, blog and documentation of this article is very good too, and as written in previous article, highly recommend Alexey Zimarev "Hands-on Domain-Driven Design with .NET Core" book and also his blog.

Empeza con esto https://spring.io/

If you want to do web apps, I'd recommend Django (a python framework) https://docs.djangoproject.com/en/4.1/, but you can do Rails, or Phoenix, or Spring Boot, or whatever. It doesn't terribly matter *which* one you do, as they share characteristics, and, chances are, your company will be using a different one :). Just pick one and go. You can do it. You know a lot more than you think.

With the idea planted, and already internalized that I would use spring-boot to create our API, I needed to decide on which engine it would be built. I had been studying Unreal Engine for some time, but because I had more know-how in Unity and because I found this AMAZING weather system, I opted for our last alternative.

This is an introduction article on how to build a RESTful application in Kotlin using Spring Boot 3 and MongoDB Atlas.

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

Im stuck between just starting up a project, or if following some starter project for learning. I did a tutorial on the spring.io website, but thats about all I have done so far.

I've been following the guides at spring.io, but there's just so many guides there. My company has a template for starting new projects (includes frontend + backend + database) so I decided to start my project using it, thinking the basic guides I followed on REST APIs would help me but I quickly realized it's more complicated than I thought.

Thanks for the advice. I followed some guides on spring.io, but because I am using a template for starting new projects provided by my company, I found most of them couldn't really translate properly to the template.

Spring makes building web applications fast and hassle-free (spring.io). By removing much of the boilerplate code and configuration associated with web development, you get a modern web programming model that streamlines the development of server-side HTML applications, REST APIs, and bidirectional, event-based systems.