DBFlow vs NHibernate

Overview

NHibernate

Stacks116

Followers92

Votes5

GitHub Stars2.2K

Forks930

DBFlow

Stacks16

Followers14

Votes3

GitHub Stars4.9K

Forks597

NHibernate vs DBFlow: What are the differences?

Developers describe NHibernate as "The object-relational mapper for .NET". It is a mature, open source object-relational mapper for the .NET framework. It's actively developed, fully featured and used in thousands of successful projects. On the other hand, DBFlow is detailed as "*Simple ORM android database library *". It is fast, efficient, and feature-rich Kotlin database library built on SQLite for Android. It utilizes annotation processing to generate SQLite boilerplate for you and provides a powerful SQLite query language that makes using SQLite a joy.

NHibernate and DBFlow belong to "Object Relational Mapper (ORM)" category of the tech stack.

NHibernate and DBFlow are both open source tools. It seems that DBFlow with 4.67K GitHub stars and 597 forks on GitHub has more adoption than NHibernate with 1.65K GitHub stars and 826 GitHub forks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

NHibernate	DBFlow
It is a mature, open source object-relational mapper for the .NET framework. It's actively developed, fully featured and used in thousands of successful projects.	It is fast, efficient, and feature-rich Kotlin database library built on SQLite for Android. It utilizes annotation processing to generate SQLite boilerplate for you and provides a powerful SQLite query language that makes using SQLite a joy.
-	Feature-rich; Kotlin database library; Built on SQLite
Statistics
GitHub Stars 2.2K	GitHub Stars 4.9K
GitHub Forks 930	GitHub Forks 597
Stacks 116	Stacks 16
Followers 92	Followers 14
Votes 5	Votes 3
Pros & Cons
Pros 5 DDD friendly	Pros 1 Open Source 1 Easy to use 1 SQLite Cons 1 Doesn't support anything other than SQLite
Integrations
.NET Visual Studio C#	Kotlin Android OS SQLite RxJava

What are some alternatives to NHibernate, DBFlow?

Sequelize

Sequelize is a promise-based ORM for Node.js and io.js. It supports the dialects PostgreSQL, MySQL, MariaDB, SQLite and MSSQL and features solid transaction support, relations, read replication and more.

Prisma

Prisma is an open-source database toolkit. It replaces traditional ORMs and makes database access easy with an auto-generated query builder for TypeScript & Node.js.

Hibernate

Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper.

Doctrine 2

Doctrine 2 sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL.

MikroORM

TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, MariaDB, PostgreSQL and SQLite databases.

Entity Framework

It is an object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write.

peewee

A small, expressive orm, written in python (2.6+, 3.2+), with built-in support for sqlite, mysql and postgresql and special extensions like hstore.

MyBatis

It is a first class persistence framework with support for custom SQL, stored procedures and advanced mappings. It eliminates almost all of the JDBC code and manual setting of parameters and retrieval of results. It can use simple XML or Annotations for configuration and map primitives, Map interfaces and Java POJOs (Plain Old Java Objects) to database records.

Entity Framework Core

It is a lightweight, extensible, open source and cross-platform version of the popular Entity Framework data access technology. It can serve as an object-relational mapper (O/RM), enabling .NET developers to work with a database using .NET objects, and eliminating the need for most of the data-access code they usually need to write.