spring-data-relational VS sagan

What do you think of Spring Data JDBC (https://spring.io/projects/spring-data-jdbc)?

What do you think of Spring Data JDBC?

Link to GitHub: https://github.com/spring-projects/spring-data-relational/blob/main/spring-data-relational/src/main/java/org/springframework/data/relational/repository/Lock.java

I would ignore the hipster jOOQ and similar and start with Spring Data JDBC https://spring.io/projects/spring-data-jdbc

This makes Spring Data JDBC a simple, limited, opinionated ORM.

Though JPA is fine, and yes hibernate can be used under the hood. When it comes to spring it is mostly what level of abstraction you want. Or you could go with JDBC. And you have a spring data JDBC for having a similar abstraction as to the JPA one.

This is not correct. You're thinking Spring Data JPA [1]. Spring Data JDBC [2] does _not_ use any Hibernate nonsense.

[1] https://spring.io/projects/spring-data-jdbc

The data moved from the awesome-but-confusing DynamoDB... into PostgreSQL✨, using Spring Data JDBC.

I didn't have much experience with Hibernate and Spring (was using JavaEE prior), it could very possibly be the case, that the team simply misused Hibernate. We might have used n+1 queries, eager loading (although I mildly remember we fixed this), oh and we had the old id generation via sequence in Hibernate, that was really pain to optimize properly. Oracle 11 does not have identity generation. I remembered this only becuase I created an issue at the time. Still not implemented, but can't blame them, who the hell uses sequences as ID generation nowadays.

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.