fabianlindfors

7 ms·

31.
by fabianlindfors 1y ago
I think specs embedded into existing code is a good idea as well, in fact there is some work being done in this area, like the Kiro editor: https://kiro.dev/ We have gone the all-specs route for now because it gives us an o
32.
by fabianlindfors 1y ago
Ah yes, we haven't spent as much effort on it as we could. Mostly been building the product itself! Pricing is still to be determined. I imagine we will charge for infra usage (processing, storage, etc) in line with other providers lik
33.
by fabianlindfors 1y ago
That's a fair take. We are planning on showing the output code to remove that need for trust, but focused on other things for the open beta. As for who it's for, we are targeting technical people who might know how to build backen
34.
by fabianlindfors 1y ago
That's a good question! > If Specific regenerates code from the spec each time (which I'm not sure it does), there's the potential for different code each time even for parts of the spec that haven't changed It doesn&
35.
by fabianlindfors 1y ago
> I think it's fair to say that you should highlight that upfront in your webpage because it's a more clear pain point than building other parts of backends. Good point! We should do that :) > My two cents: in my experience
36.
by fabianlindfors 1y ago
That's fair! We have considered how we could offer an open-source version of Specific but haven't found a good model for it yet. We are definitely open to it though! Curious to hear more about the entity relationship definition. T
37.
Show HN: Specific (YC F25) – Build backends with specifications instead of code(specific.dev)
29 points by fabianlindfors 1y ago|14 comments
38.
Next.js is not a good fit for vibe engineering(fabianlindfors.se)
3 points by fabianlindfors 1y ago|0 comments
39.
by fabianlindfors 1y ago
That's right. Largely the same result can be achieved with a unique index though, which I'm working on adding support for right now.
40.
by fabianlindfors 1y ago
Certainly complicated! This is one of those places where I don't think Postgres compatibility is achievable or even desirable, schema changes in a distributed databases are a whole different beast (and very complicated in large Postgre
41.
by fabianlindfors 1y ago
> I've not paid much attention to the Postgres extension API, but I'm pleasantly surprised it's that flexible. I've been hearing for years about how Postgres pluggable engine interface isn't flexible enough to im
42.
by fabianlindfors 1y ago
> What this project is doing allows one to represent each row (tuple) as a FDB key/value, giving you finer-grained control. But it comes at a cost of having to implement all the access methods, including index scans, in terms of FDB
43.
by fabianlindfors 1y ago
A table access method can decide itself if it wants to use the PG buffer cache, pgfdb does not so it's irrelevant in that case. > Also, how do the deployment semantics of FDB affect this. If I remember correctly, you typically run o
44.
by fabianlindfors 1y ago
Glad you like it! You don't need to recompile it actually! It's enough to compile your extension and Postgres can then dynamically link to it, which makes for a perfectly good feedback loop. pgfdb is built with pgrx: https:/
45.
by fabianlindfors 1y ago
This is my project, thanks a lot for posting! If anybody happens to have questions, I'm happy to answer them
46.
by fabianlindfors 1y ago
Super cool project and the code is delightfully readable as well! I had the pleasure of having Erik advise me for my thesis on distributed databases a few years ago. I’m very lucky to have had the chance to tap into his knowledge on all thi
47.
by fabianlindfors 1y ago
Yes, definitely, getting these things right I think are key to making the project actually work. Currently just experimental so we'll see!
48.
by fabianlindfors 1y ago
If anybody wants to follow along, I'll be publishing it here once ready: https://github.com/fabianlindfors/pgfdb (currently just an empty repo!)
49.
by fabianlindfors 1y ago
Neon encounters a similar problem and performs prefetching of pages before Postgres wants to read them: https://neon.tech/docs/extensions/neon#prefetch-option
50.
by fabianlindfors 1y ago
The five second timeout remains and trickles through to apply to Postgres transactions instead. This project would very much be for OLTP, so not really fit for using Postgres for OLAP or hybrid workloads. The N+1 issue is a really interesti
51.
by fabianlindfors 1y ago
Really cool although quite an undertaking to build an entire SQL engine! I have been working on something pretty similar but using Postgres instead. Basically extending Postgres to run stateless on top of FoundationDB, which would achieve t
52.
by fabianlindfors 1y ago
Yes, pretty similar although I don't think TiDB is actually built on top of MySQL, instead it just reimplements the protocol for compatibility. My project is actually an extension of Postgres, which hopefully means much better Postgres
53.
by fabianlindfors 1y ago
I’m working on extending Postgres to run on top of FoundationDB. The goal would be turning Postgres into a distributed, horizontally scalable database with automatic sharding and replication. Hoping to share a first version of it soon. It’s
54.
by fabianlindfors 2y ago
Sure! So my prototype is implemented as a Postgres extension that hooks into transaction as well table and index storage and implements them on top of FoundationDB. This makes Postgres itself stateless and all data storage and transaction p
55.
by fabianlindfors 2y ago
I've been working on extending Postgres to run on top of FoundationDB, effectively turning Postgres into a distributed database with all the modern features one would expect. Hoping to release an initial version for people to try out v
56.
by fabianlindfors 2y ago
My project Reshape ( https://github.com/fabianlindfors/reshape ) might be interesting to you, it's a bit like blue/green DB deployments in that it uses a two-step process where it can support both the old and t
57.
by fabianlindfors 2y ago
For people interested in this subject, you might also be interested in my project Reshape: https://github.com/fabianlindfors/reshape . It takes database migrations a step further than most tools, guaranteeing zero-downt
58.
by fabianlindfors 2y ago
> I assume you're thinking of using FoundationDB as a page store, much like https://github.com/neondatabase/neon uses S3? Actually not, I'm replacing Postres storage entirely down to the tuple level with F
59.
by fabianlindfors 2y ago
I've been experimenting with customizing Postgres to run on top of FoundationDB, which to me would be the dream combination of Postgres' top-notch feature set and ecosystem with FoundationDB's unique resilience, scalability a
60.
by fabianlindfors 2y ago
Unfortunately nothing yet. Feel free to hit me up at the email in my profile and I'll let you know if I do write something up. Another pretty cool fact is that I've so far managed to build the entire thing without having to fork P

More ›