nimforum VS CouchDB

If the video example does not work, you can use the examples projects in the nim SDL repository. When ex101_init.nim works, there is no reason the video example does not work. If you have further issues, do not hesitate to share a minimal working example with your detailed configuration (Nim compiler version, command line you used, file directory, libraries installed) on the forum.nim-lang.org

It might be worth posting this on the official nim forum (https://forum.nim-lang.org/) to cast a wider net.

Obviously forums aren't as popular as they used to be, so this topic might not be of interest to many. For folks that want to run a forum, they'd most certainly go with Discourse (Ruby), Flarum (PHP), Xenforo (PHP), NodeBB (Javascript), Nimforum (Nim) and maybe Casnode (Go)

https://forum.nim-lang.org/ doesn't let me post.

NimForum - https://github.com/nim-lang/nimforum

You sound like you are in just the right demographic to love Nim...The Forum [1] is a good place to get support.

https://forum.nim-lang.org/

"embedded" can mean a few different things so that's a bit confusing for me, but if the intent was "show me places sqlite is used as a database backend for user-facing web software", the Nim forum (https://github.com/nim-lang/nimforum) uses sqlite as its database backend.

I love NimForum, like a simplified discourse and super light on resources. Example

https://forum.nim-lang.org

uses sqlite, is actively improved, they claim the nim language makes small cross-platform binaries but none for this release it seems.

CouchDB

CouchDB is a json based database for simple projects. The fork pouchdb offers lots of support for offline.

Apache CouchDB belongs to the family of NoSQL databases. It is a document store with a strong focus on replication and reliability. One of the most significant differences between CouchDB and a relational database (besides the absence of tables and schemas) is how you query data. Relational databases allow their users to execute arbitrary and dynamic queries via SQL. Each SQL query may look completely different than the previous one. These dynamic aspects are significant for use cases where you work exploratively with your dataset but don't matter as much in a web context. Additionally, defining an index for a specific table is optional. Most developers will define indices to boost performance, but the database does not require it.

I just turns out you can't always do that in a real codebase. For example see here:

  https://github.com/apache/couchdb/blob/23efd8e5b1aa96ef01640fec03a5fedc945ba8b9/src/couch_mrview/src/couch_mrview_http.erl#L228

Example: Apache Cassandra, CouchDB.

For non-SQL-based databases, consider MongoDB, or CouchDB, which are very easy to get started with.

The Apache CouchDB server. It stores Annotation data.

CouchDB