synthmeat
Joined 11 years ago
Karma
1,745
Submissions
320
Member since
Feb 15
[ mail: synthmeat at world's favorite mail provider dot com ]
View on Hacker NewsRecent submissions
Comment · 1 year ago
I'm not sure about the paper and claims on the whole but the Hanoi part has received some shade here https://x.com/scaling01/status/1931783050511126954
Comment · 1 year ago
Supra-aural headphones with a spherical camera rig would be really powerful ambient for first big AI-first product.
Comment · 2 years ago
To voice support for current state - do what you're already doing, and I agree on focusing on opening up the format.
Don't hesitate to charge for v2, if improvements pile up and you have affordances to do so. Will gladly pay.
It's pretty great already as-is. Thank you.
Comment · 3 years ago
You can read more about it here https://www.mongodb.com/docs/manual/changeStreams/
My feeling is that database needs to be built with replication in mind from the get-go to have something like this work well.
Comment · 3 years ago
MongoDB has had ChangeStreams for a long time now.
Comment · 3 years ago
Schema-less is a bit wrong term, since you always end up with one but, indeed, schema-on-read vs schema-on-write discussion for individual use cases is far from a settled thing, even though the zeitgeist is that schema-on-write won sometime in the 70s.
You say "prototyping", but I would generalize that to "faster evolving" in the long term. Of course, not without tradeoffs.
I personally have zero issues writing a custom marshaller when needed for any the schema-less document collections I have. Constraints your application has on the data are a superset of db schema anyways.
Comment · 3 years ago
Just to add to sibling comments, one killer feature for me is ChangeStreams[1]. It's miles ahead of what Postgres[2] offers, and it enables really interesting use cases. Some of my services built around ChangeStreams end up not doing a single query to the DB. Data is right there in the program memory, indexed how I need it to be, and program is immediately reactive to any changes in the DB.
[1] https://www.mongodb.com/docs/manual/changeStreams/
[2] https://blog.sequin.io/all-the-ways-to-capture-changes-in-po...