Skip to main content
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Tweeted twitter.com/StackSoftRecs/status/1273042712133095425
added 123 characters in body
Source Link

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probably to store small pictures in the future too

I need the database:

  • to be lightweight
  • to be embedded
  • to be created per each user
  • not to be used by more than one user at time
  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLite or other solutions? Since the database must be embedded I shall probably choose from:

  • SQLite
  • SQL Server Compact
  • Firebird Embedded
  • Couchbase Lite
  • LiteDB

LiteDB has got it all: it's lightweight, modern, noSQL, scalable, encryption is out of the box and supports .NET Core. Any cons? Couchbase needs Enterprise Edition for encryption and the other databases are SQL or/and obsolete.

Does LiteDB have any cons?

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probably to store small pictures in the future too

I need the database:

  • to be embedded
  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLite or other solutions? Since the database must be embedded I shall probably choose from:

  • SQLite
  • SQL Server Compact
  • Firebird Embedded
  • Couchbase Lite
  • LiteDB

LiteDB has got it all: it's lightweight, modern, noSQL, scalable, encryption is out of the box and supports .NET Core. Any cons? Couchbase needs Enterprise Edition for encryption and the other databases are SQL or/and obsolete.

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probably to store small pictures in the future too

I need the database:

  • to be lightweight
  • to be embedded
  • to be created per each user
  • not to be used by more than one user at time
  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLite or other solutions? Since the database must be embedded I shall probably choose from:

  • SQLite
  • SQL Server Compact
  • Firebird Embedded
  • Couchbase Lite
  • LiteDB

LiteDB has got it all: it's lightweight, modern, noSQL, scalable, encryption is out of the box and supports .NET Core. Couchbase needs Enterprise Edition for encryption and the other databases are SQL or/and obsolete.

Does LiteDB have any cons?

added 404 characters in body
Source Link

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probably to store small pictures in the future too

I need the database:

  • to be embedded
  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLite or other solutions? Since the database must be embedded I shall probably choose from:

  • SQLite
  • SQL Server Compact
  • Firebird Embedded
  • Couchbase Lite
  • LiteDB

LiteDB has got it all: it's lightweight, modern, noSQL, scalable, encryption is out of the box and supports .NET Core. Any cons? Couchbase needs Enterprise Edition for encryption and the other databases are SQL or/and obsolete.

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probably to store small pictures in the future too

I need the database:

  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLite or other solutions?

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probably to store small pictures in the future too

I need the database:

  • to be embedded
  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLite or other solutions? Since the database must be embedded I shall probably choose from:

  • SQLite
  • SQL Server Compact
  • Firebird Embedded
  • Couchbase Lite
  • LiteDB

LiteDB has got it all: it's lightweight, modern, noSQL, scalable, encryption is out of the box and supports .NET Core. Any cons? Couchbase needs Enterprise Edition for encryption and the other databases are SQL or/and obsolete.

edited body
Source Link

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probableprobably to store small pictures in the future too

I need the database:

  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLlightSQLite or other solutions?

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probable to store small pictures in the future too

I need the database:

  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLlight or other solutions?

I am about to choose a database solution for my c# project:

  • to store simple configuration at first, bools, ints, paths etc.
  • to store lots of small text blocks in the future
  • probably to store small pictures in the future too

I need the database:

  • to be free or very cheap
  • transactions to be reliable
  • to be scalable
  • to be encrypted or at least masked

Initially I thought about some NoSQL, text databases but is it the correct path? How about SQLite or other solutions?

deleted 39 characters in body
Source Link
Loading
Source Link
Loading