hasyimibhar

3 ms·

1.
by hasyimibhar 21d ago
The homepage shows an example of an agent accidentally dropping a table. 1. This is such an insane example, I don't get why would you give agents write access to your production db in the first place. Are people really doing this? I do
2.
by hasyimibhar 1mo ago
Having worked at a large company that misuses feature flag service for everything, here are some examples why you shouldn’t: - one team uses feature flag for product gating. Feature flag service goes down. Users temporarily got locked out o
3.
by hasyimibhar 2mo ago
> Examples? Ok -> Let us look at data storage. > They got D1 (SQLite serverless), Durable Objects with their own SQLite, KV, R2, Queues, and Hyperdrive to speed up external Postgres or MySQL. Maybe it's just me, but I don&#x27
4.
by hasyimibhar 2mo ago
DMS is so unreliable though.
5.
by hasyimibhar 2mo ago
I’m waiting for Cloudflare R2 to eventually support mirroring Postgres into R2 catalog. It seems like a nice fit because they already have R2 SQL.
6.
by hasyimibhar 2mo ago
Yes I’m not suggesting to do this inside Postgres. I’m hoping that a Postgres provider can provide this mirroring capability out of the box, similar to how they provide a connection-pooled endpoint out of the box so I don’t have to self-hos
7.
by hasyimibhar 2mo ago
It's interesting to watch how different companies that offer both Postgres and warehousing solution under 1 roof approach the same problem: - ClickHouse focuses on traditional CDC (ClickPipes) and just make it blazingly fast - Databric
8.
by hasyimibhar 2mo ago
> Almost always they end up setting up a separate system such as Clickhouse and replicating the data between the two systems. Now they can have one system that's Postgres-compatible, and it's faster than either of the original
9.
by hasyimibhar 2mo ago
I'm guessing it's something like MongoDB TTL index[0]. It's useful for huge append-only tables where you want a row to be automatically removed after a period of time. The postgres approach is usually to partition your table
10.
by hasyimibhar 2mo ago
Sorry but that is not pixel art.
11.
by hasyimibhar 2mo ago
If your domain is analytics-heavy, don't try to optimize your Postgres for analytics. Follow the standard pattern of mirroring your data to a data warehouse and go to town there instead. There will be upfront cost of having to pay for
12.
by hasyimibhar 3mo ago
As a parent with 3 kids and both my wife and I working, folding clothes is the most tedious household chore. It's physically and mentally exhausting (unlike doing the dishes, which is only physically exhausting as I can wash piles of d
13.
by hasyimibhar 3mo ago
I'm surprised no one has mentioned Multigres yet, they are the competitor of Neki. I'm a big fan of both and has been following them since they were announced last year. I think this blog post is the first time they are talking ab
14.
by hasyimibhar 3mo ago
At huge companies, it's hard to prioritize this because it's hard to pin dollar values to removing legacy code, while it's easier to show how building feature X will earn the company $Y amount of revenue. And because of that,
15.
by hasyimibhar 3mo ago
How does LTAP architecture deals with major Postgres upgrade? Is it truly zero-downtime for both upstream and downstream?
16.
by hasyimibhar 3mo ago
> If you have something like dolt (not affiliated), a version controlled database, you wouldn’t have to slap change dates on anything OR create your historical table. The changes would be implicit in the version history. Nope, even if I
17.
by hasyimibhar 3mo ago
It wouldn't be possible to do this with LTAP architecture since (I'm assuming) the individual logical changes are not visible. But honestly I've always seen SCD type 2 table as a workaround due to lack of data modeling experi
18.
by hasyimibhar 3mo ago
How does it compare to a full-fledged durable execution platform like DBOS[0], which follows the same philosophy? Looks like River does have workflows, but it's locked behind Pro [1]. [0] https://dbos.dev [1] https:/&
19.
by hasyimibhar 4mo ago
What about Multigres[0]? It builds on top of Postgres and adds HA (based on Flexible Paxos[1]), sharding, etc. They're still not production-ready, but I'm highly optimistic they will solve a lot of the problems Postgres have. For
20.
by hasyimibhar 4mo ago
It is also easier to make your code deterministic with Rust vs with Go, which is incredibly useful if you need to perform deterministic simulation testing + property-based testing. I recently wrote a Postgres-to-Iceberg data mirroring tool
21.
by hasyimibhar 5mo ago
The problem with the us-east-1 outage is that a lot of big companies are there, so even if you try your best not to depend on us-east-1, your third party providers are most likely there. In my previous company, we were completely down durin
22.
by hasyimibhar 5mo ago
In some cases you have no choice but to retain the data, e.g. due to compliance. But the good thing is it doesn't have to be in Postgres. You can periodically offload data to a lakehouse, then delete it from Postgres. If the table is p
23.
by hasyimibhar 5mo ago
How does Lakebase compare to OrioleDB[0]? [0] https://www.orioledb.com/
24.
by hasyimibhar 5mo ago
You should check them out, their interface pretty much looks like chat nowadays.
25.
by hasyimibhar 5mo ago
How does this compare to open source Deepnote[0]? We use the cloud version (BYOC) at my previous company to replace self-hosted Jupyter notebooks, and it's pretty great. [0] https://github.com/deepnote/deepnote
26.
by hasyimibhar 5mo ago
I mean that's what the Vega team is doing no? They are building the standard grammar (Vega-Lite), along with an implementation (Vega). And they are already quite established with rich ecosystem, and supports a ton of components[0]. The
27.
by hasyimibhar 5mo ago
Why not use Vega-Lite[0]? It’s my go-to data viz DSL with Claude. [0] https://vega.github.io/vega-lite/
28.
by hasyimibhar 5mo ago
You can skip by running git commit --no-verify. I know this because I also hate pre-commit checks, and I will automatically use it when working with any codebase that has one.
29.
by hasyimibhar 5mo ago
Having worked at enterprise with 100+ engineers across multiple teams with complex reporting lines, I definitely agree with this. There's a lot of nuance behind decisions that docs simply can't capture. I mean in theory you can pr
30.
by hasyimibhar 5mo ago
AFAIK that's what Multigres[0] and Neki[1] are trying to solve. [0] https://multigres.com/ [1] https://neki.dev/

More ›