The AWS and MongoDB Infrastructure of Parse

Re:The AWS and MongoDB Infrastructure of Parse by pmelendez on Thursday February 09, 2017 @05:53AM (#13606019)

"searching through around 200 million tuples within the order of 2 seconds (partially stored columnar using psql array types and GIN indexes). Not for a second did I consider using any kind of specialized database, nor optimized algorithms, except for some application-level caching. "

That's cool and all, but for some real-time applications, retrieving in the order of seconds is unacceptable.

DBMS has their earned place in the backend stack but I found that statement of covering 98% of the cases a bit of a stretch.

[ Parent | on HN ]

Re:The AWS and MongoDB Infrastructure of Parse by edejong on Thursday February 09, 2017 @06:12AM (#13606102)

Of course, this is an extreme example. Most of our front-end is able to serve quite complicated data within 500 milliseconds. Some queries are over a longer time-span (3 months, 0.7 million truck-movement-legs, +/- 200M links), so a 2 second wait-time (including a spinner) is sufficient.

[ Parent | on HN ]