ORM vs Core Database Driver

Sami Salih İbrahimbaş — Mon, 25 Jul 2022 19:57:00 +0000

Greetings, in this article we will briefly talk about the comparison of ORM and database drivers and which one you should perfer in which situation.

ORM Pros and Cons

Pros

Schemas/Entites are clearly defined.
Relatively easy to understand and develop
You can write basic Queries with built-in query-builders
You don't bother too much with database operations

Cons

Low performance
As it is a pattern applied on top of the engine, it may restrict some advanced operations
Extra dependencies and possible size growth for the project (the item may sound trivial but will be important when using docker and etc.)

Database Driver Pros and Cons

Pros

High performance
Takes up minimal space
Trouble-free guarantee and full documentation as it was developed by the database company

Cons

May require expertiese with queries and databases
Schemas are not clearly defined or have no effect on the database

When, Which?

If you are developing a simple demo, developing a blog, or if time and performance (included build time and performance) is not important to you; your choice should be ORM.

If time and performance (included build time and performance) is your thing, if you're a database expert; your choice should be Core Database Driver.

Here is an article measuring the differences between mongodb and mongoose, there is a really big performance difference.

If you're lazy, there's a table like this at the end of the article.

READS	Native	Mongoose
Throughput	1200 #/sec	583 #/sec
Avg Request	0.83 ms	1.71 ms

WRITES	Native	Mongoose
Throughput	1128 #/sec	384 #/sec
Avg Request	0.89 ms	2.60 ms

Whay do you think about this subject?

With Dynamic SQL Queries on TypeScript & NodeJS

Sami Salih İbrahimbaş — Fri, 10 Jun 2022 19:01:17 +0000

Hello,
In this article, I will show you how to write a more dynamic, fast and sustainable SQL queries with @ssibrahimbas/query package, which is the npm package I wrote with my own keyboard.

This package creates you SQL queries. But it doesn't run them. We usually use ready-made SQL clients (like sequelize, pg) to run SQL queries in NodeJS. I developed this package only as a query-builder by making use of the Single Responsibility pattern. It's the job of sequelize or pg to execute the query. Whichever you want!

Let's install the npm package

npm install @ssibrahimbas/query

for yarn yarn add @ssibrahimbas/query

Okey, now let's create an index.js file and code it

const { Query } = require("@ssibrahimbas/query");

console.log(
  Query.table("users").select("id", "name").where("id", "=", 1).getAll()
);

The process here is to create the query that returns the id and name field if id 1 from the users table.

When we run the code we will get the following result:
SELECT id FROM users WHERE id = '1'

Better install a driver and give it a try on the real database! It was developed entirely with TypeScript, full support for TypeScript & JavaScript and has +50 unit tests. And the documentation is pretty good too!

I would be grateful if you share your experiences as comments.

Npm Package

DEV Community: Sami Salih İbrahimbaş

ORM vs Core Database Driver

ORM Pros and Cons

Pros

Cons

Database Driver Pros and Cons

Pros

Cons

With Dynamic SQL Queries on TypeScript & NodeJS