4 ms·
Would be interesting to hear how they arrived at the RethinkDB/Elasticsearch combination over Postgres at the start of the project. It doesn't seem they lost an
by dm3 9y ago
Would be interesting to hear how they arrived at the RethinkDB/Elasticsearch combination over Postgres at the start of the project. It doesn't seem they lost any features after the transition. Was something lacking in Postgres at the time of initial implementation?
- chris_st 9y agoHowever, they do say: > leaning heavily on Haskell in order to fill in some of the gaps quickly. So it looks like they had to do some work to cover some features from rethinkdb/elasticsearch.
- fmap 9y agoThe code in the post is just used to migrate from an untyped interface to a typed one. Unless I'm missing something, there seems to be no mention of any missing features in postgres.
- Yeroc 9y agoThey did mention missing JSON schema validation in Postgres.
- billrobertson42 9y agoAnd also many mentions of no schema validation in Rethink, so that's probably not a gap.