>2017 >using mongoloid DB How many of you fell for the meme?

Not sure what else to use if you want to store/manipulate images.
Storing them as binary blobs in Postgres just seems weird.

>>61847133
our project management, sadly, despite the fact we're building a event-driven service and half of the team suggested datomic...
fuck mongoDB

>>61847698
Why? Postgres works fine with blobs.

Also in most cases you don't have the same requirements for images as for your valuable data, so just store them in filesystem.

>>61847777

I thought about using Heroku until I found out they have this stupid "ephemeral file system" when you can't reliably store anything outside of your database.

Woud it be feasible to store small images (avatar pics for a forum) in a PostgreSQL? Or is this to difficult/slow?

>>61847133
>not converting your data to dna sequence and storing in blastdb

>>61847133
It's stupidly easily to use with node because you can use Json in and json out.

It's kind of a meme but it has uses.

>>61847929
It's trivial.

Just store stuff in files.

>>61847133
Document stores are not a meme. Non relational databases are the future, you mong.

>>61847133
But our products are now 400% faster than when we used a RDBMS... Mongodb is bretty gud

needed for elasticsearch.