jordanchan

7 ms·

1. 31.▲
   by jordanchan 11y ago

   True, as I was designing the tables, I was surprised to notice how normalized it looked. The generic kind of queries you mention: actually, yes, I think I will need them. Your second point on downsides is something I have/had to think
2. 32.▲
   by jordanchan 11y ago

   Thanks for the feedback. Indeed, one of the reasons behind inheriting tables was to use partial indexes - which should help with performance. Another was ease scaling out, if needed. Using the @> operators on array columns is something I
3. 33.▲
   by jordanchan 11y ago

   You said it! Actually, Facebook's TAO was an early inspiration for me as well, but it is really customized and complex too, so probably not something for a tiny team. But the concepts from TAO are applicable to many similar scenarios.
4. 34.▲
   by jordanchan 11y ago

   Graph db's are a very good idea. Its just that the solutions in the market are not very mature yet, and the community is not very large yet. Most of the downsides stem from these two facts. So unless the solution you're building h
5. 35.▲
   by jordanchan 11y ago

   Agreed, my reasons for coming back to Postgres are quite similar. In general, one only needs to go a few layers in the graph. Recursive queries are needed for specific use cases. Even then, querying from the app, like you said, and/or
6. 36.▲
   by jordanchan 11y ago

   Of course, JSON is a good way to store ad hoc, or new relations which haven't yet been structured. But for frequently occurring relations, I'm preferring separate tables instead of JSON for ease of querying and joins. If number of
7. 37.▲
   by jordanchan 11y ago

   Thanks! That's a useful technique..
8. 38.▲
   Ask HN: Implementing a graph database using Postgres tables for nodes and edges?

   87 points by jordanchan 11y ago|60 comments
9. 39.▲
   by jordanchan 11y ago

   Yes, of course. So did Russia. See the movie Farewell, based on actual events? http://www.rottentomatoes.com/m/farewell_2010/ The point being, if they could, and if it helped them, and if there was no real/st
10. 40.▲
    by jordanchan 11y ago

    Ah, sure! Good that you brought it up. Such questions were actually considered, but the answers arrived at were always vague and changeable. Not surprising for a startup I guess. Much of it will be read heavy, some parts will be write heavy
11. 41.▲
    by jordanchan 11y ago

    Thanks for the feedback. So they're basically comparable, with a slight edge for MySQL. Guess I will play with both and pick whichever feels more handy. I have seen many discussions on Postgres and MySQL on hacker news, so I thought I
12. 42.▲
    by jordanchan 11y ago

    Yes, it is possible to recapture the experience. 1. There's a lot more than deep learning and genome editing. But yes, you're right, these are part of the cutting edge. You should look around further. And beyond pure technology to
13. 43.▲
    Ask HN: PostgreSQL or MySQL with Node.js?

    3 points by jordanchan 11y ago|4 comments