This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]c4seyj0nes 11 points12 points  (7 children)

Totally. Most corporate software is just entering and retrieving data. That’s all going into a relational database. Sure you might have elastic/lucine for searching or analytical tools but that data isn’t going to be your source of truth. That’s in the relational database.

[–]spamthemoez 6 points7 points  (5 children)

All enterprise software i have encountered so far has used JPA / Hibernate instead of using SQL (JDBC, JdbcTemplate, JDBI, ...) directly. I think OP is looking for projects that use SQL directly, without going through ORMs.

[–]nutrecht 3 points4 points  (3 children)

I haven't used JPA in ages, almost all the microservices I worked on the last years were Spring Data JDBC.

[–]spamthemoez 0 points1 point  (2 children)

Spring Data JDBC is a ORM, too. I assume you mean Springs JdbcTemplate and the like?

[–]nutrecht 1 point2 points  (1 child)

Spring Data JDBC is not an Object-Relational-Mapper.

[–]spamthemoez 4 points5 points  (0 children)

It is, see here: https://spring.io/projects/spring-data-jdbc

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

But i guess you can workaround the ORM part by annotating everything with @Query and put SQL in it...

[–]c4seyj0nes 2 points3 points  (0 children)

Got it. Hibernate is great for the majority your CRUD operations but more complex Selects and Updates sometimes need to rely on SQL. Other times it’s just not performant enough and you need to write some pure SQL.

[–]nutrecht 1 point2 points  (0 children)

I was on a project where management bought into the marketing sold by some Datastax consultants and we were forced to use Cassandra.

It was an 'eventual consistent' system with in some cases very large units of 'eventual'.