Re:What ORMs have taught me: just learn SQL (2014)
by wwweston on Saturday September 21, 2019 @05:57PM
(#21038156)
What kind of concurrency issues were you running into with a RDBMS that has atomic transactions?
Are we talking about distributed store situations where CAP theorem limits apply, or something else?
Re:What ORMs have taught me: just learn SQL (2014)
by collyw on Saturday September 21, 2019 @08:17AM
(#21034868)
I see the same problems but it usually caused by a reluctance to modify the database schema. Once you get comfortable doing that and keep your schema matching the requirements then it solves a lot of the problems.
A lot of software design runs like this: (1) translate business patterns into a relational schema; (2) build interactions with that schema; and (3) as that gets harder, use SQL arcana and ORMs and views and stored procedures to squeeze out flexibility.
I worked like this for the first decade of my career. My systems got some use, and struggled along, but they are failed projects.
Repeatedly I had this feeling: the project is almost done, but there are some concurrency issues where I would not even know how to start addressing them.
The database-centric design made it impossible to work past that.
After much searching, I came to this: Stored State is a brittle and unwieldy thing, and you want as little of it in your life as possible. The more you have, the harder you have to work to get anything done. Databases are an institution of Stored State.
As an alternative, you can derive state from messages.