Explore >> Select a destination
|
You are here 
|
surfingcomplexity.blog | ||
| | | | |
www.eliza-ng.me
|
|
| | | | | In the world of Java development, one topic that has sparked debate and frustration for many developers is Object-Relational Mapping (ORM). ORM is a technique used to bridge the gap between object-oriented programming languages, such as Java, and relational databases, like MySQL or PostgreSQL. The purpose of ORM is to simplify the data access layer and eliminate the need for developers to write raw SQL queries. However, a recent text expressing strong criticism of ORM on Java, particularly Hibernate, has garnered attention among developers. The author claims that ORM, in general, has always been a disappointing solution. One of the arguments presented is that the ability to use different databases, which was once touted as a selling point of ORM, is a feature that is rarely utilized in practice. Furthermore, the claim that developers don't need to know SQL while using ORM is dismissed as false, as modifying queries at the string level is often necessary in non-trivial applications. | |
| | | | |
timilearning.com
|
|
| | | | | Have you ever wondered how data stored in databases actually gets represented on your computer's hard disk? Or why some queries to your database tables benefit from adding indexes on columns? Well, whether you have or not, here's a series of posts that aim to detail my understanding of the journey from inserting a row to a database table, to actually retrieving that row. | |
| | | | |
architecturenotes.co
|
|
| | | | | How Relational Databases Work. This post talks about how indexes and transactions work on the inside of relational databases. | |
| | | | |
www.adamconrad.dev
|
|
| | | Ch 5 of my book club review of Designing Data-Intensive Applications by Martin Kleppmann. | ||
