DGraph for smaller projects / low-resource contexts

Oh not not to say it’s a problem with the standalone image it’s just a different entrypoint on the normal dgraph image. Just a problem with running a single copy of anything, which the standalone image is.

The OOM was an example of something that can cause a file to not be fully fsynced to flush say the manifest state in badger for example.

Unfortunately I keep coming across issue after issue where dgraph/badger completely corrupts between one node or even one whole group of nodes

At least with the single node failure I can replace it.

1 Like