mrjn
Joined 12 years ago
Karma
899
Submissions
361
Member since
Nov 24
https://manishrjain.com/about
View on Hacker NewsRecent submissions
Comment · 4 days ago
Author here. Egres is a Postgres-compatible database designed to tackle heavy workloads and run thousands of tenants on the same server. It works with psql and drivers unchanged. Right now the query ability is limited, and would grow with future releases. The post goes into details about the what, why and how; which I hope you'd find interesting.
Before Egres, I was the founder of Dgraph -- author of Dgraph and Badger. ex-Google, ex-Uber. So, been working on databases for a while now. The idea for Egres all started with a question: "“What would Postgres look like if it were to be designed today?” After years of pondering and a year of work, the result is Egres.
For Egres, I wrote a new storage engine called zdb, which is pioneering LSM forest concept -- a tree of LSM trees. zdb can run on local disk or object storage, has native roaring bitmaps integration, can do instant zero-copy branches for database or table.
All of this runs on a custom co-routine system I wrote called zfiber, so all queries execute on that. Egres meters CPU ticks, disk IOPS and memory used per query, per tenant, so it can run thousands of tenants on the same server without noisy neighbor problem.
This release is single node, but Raft replication is already baked in. Future releases would allow multi-node clusters.
Install: curl -fsSL https://egresql.io/install.sh | sh. Repo: https://github.com/manishrjain/egres.
Would love to know your thoughts, and which features to prioritize getting into next release.
Comment · 6 months ago
skiplists form the basis of in-memory tables used by LSM trees, which are themselves the basis of most modern DBs (written post 2005).
Comment · 6 months ago
Talking about dark modes, nytimes still doesn't have an official dark mode (or not I can easily see). This should help.
Comment · 1 year ago
Wouldn't a Vitess for Postgres look like a Yugabyte?
Comment · 2 years ago
This would be a bigger problem in community use cases. We're going to introduce a trust level system to tackle this, inspired by Discourse:
https://blog.discourse.org/2018/06/understanding-discourse-t...
Comment · 2 years ago
Thank you! We went through many iterations to get to this pricing model. So, I appreciate this comment.
Comment · 2 years ago
OpenAI has strict privacy rules in place. Being on a business account, any of the data that we send to OpenAI wouldn't be used for training.
It's a SaaS. Over the next few months, we'll be going through the SOC2 compliance process.
Will update the footer, thanks for catching.
Comment · 2 years ago
https://struct.ai/struct-for-slack would allow individuals to use Struct as an interface to Slack, without the whole team having to switch in one go.
Comment · 2 years ago
Perhaps a good start would be to create a Struct org, for communicating within the team?
We'd surely look into Teams integration at some point. Though, I'm not sure how many takers would be there for Teams/Struct integration. My perception is that Teams users tend to be medium-to-large businesses who are tied to Microsoft Office, and would be very hard to sell to. I might be wrong.
Comment · 2 years ago
Fair point. We can all do with less meetings. I think tools like chat platforms / loom are all aimed at reducing the number of meetings we need to do.
Though, you do have to abide by Metcalfe's law. Most modern work happens in teams and therefore, you have to pay the price of O(N^2) communication, where N = size of the team.
I don't see communication decreasing overall. We just have to use the right tools to be more effective at it.
Comment · 2 years ago
This should help: https://struct.ai/struct-for-slack
Comment · 2 years ago
Could be a feature request to integrate with Matrix APIs. For example, we're doing bidirectional sync with Slack already. And unidirectional sync with Discord.