Using databases without putting domain logic in them

Published
Aug 10, 2023
Written by
Benjamin Crozat
0
comments
1 minutes
read

In this article, Alex Kondov shares why it’s crucial not to store domain logic in databases while still utilizing them to their full extent.

He bases his argument on maintainability difficulties and threats to the separation of concerns, emphasizing the downside of splitting logic between the application and its storage. He also gives practical examples of improving the utilization of database capabilities without adding domain logic. One such case involves handling user reactions to data using application-level functionality rather than database triggers.

Kondov’s central point revolves around the importance of using databases as holders of information instead of decision-making tools.

About Benjamin Crozat
Benjamin Crozat

Hi! I’m from the South of France and I’ve been a self-taught web developer since 2006. When I started learning PHP and JavaScript, PHP 4 was still widely used, Internet Explorer 6 ruled the world, and we used DHTML to add falling snow on websites.

Being able to educate myself for free on the web changed my life for the better. Giving back to the community was a natural direction in my career and I truly enjoy it.

Therefore, I decided to take action:

  1. I launched this blog in September 2022 with the goal to be in everyone’s Google search. I get more than tens of thousands of monthly clicks from it and even more visits overall (my analytics dashboard is public by the way).
  2. I also started growing my X (formerly Twitter) account at the same time, which has now over 7,000 followers.
  3. All the content I write is free thanks to my sponsors.

I also want to be completely free with my time and make a living with my own products. In April 2024, I launched Nobinge, a tool to summarize and chat with your content, including YouTube videos.

Believe me, I’m just getting started!

0 comments

You need to be signed in to comment this post.
Sign in with GitHub