dockerized CouchDB and performance

[maxlath]

extract of the article Database Deep Dives: CouchDB:

For certain workloads, the technology isn’t quite there yet. Not saying Docker is the only container solution or Kubernetes is the only distribution situation that we can get into, but CouchDB—as a distributed database—makes prime use of low-latency, high-bandwidth networking and extremely fast IO throughput and disk access.
In certain scenarios that are getting smaller and smaller, both Kubernetes and Docker get in the way of that. At that point, CouchDB gets slow, or you get timeout errors, that you can’t explain. In the grand scheme of things, if you build an app that knows how to retry things, it’s not a big problem, but it is a moving target.

Just to keep this kind of consideration in mind. Now that the apt install seems to be possible again, it might make sense to keep deploying in prod without Docker.

[jum-s]

well its also possible to apt couch inside the inventaire container

[maxlath]

that wouldn't change the fact that there would still be a container layer behind CouchDB and the disk

[jum-s]

even if its in the same container ?

in any case according to some SO science (sic), it seems discouraged in general. But dbs which are not "stressed" a lot seems fine.

[jum-s]

the source you mention also points it

If you have low resource requirements but want to get the benefits of running inside of a container —sure, go for it, just know the [limits of certain metrics]

[woj-tek]

Is CouchDB performance still an issue? Original link seems to change it's contents and doesn't mention the performance issue at all...