fabianlindfors

6 ms·

61.
by fabianlindfors 2y ago
FoundationDB endlessly interests me and even though the record layer is nice, my dream would be a proper SQL layer. I've been experimenting with making Postgres run on top of FoundationDB, effectively making Postgres a stateless layer
62.
by fabianlindfors 2y ago
See my other comment. Unfortunately Cockroach doesn't do much in terms of helping with zero-downtime schema migrations :/
63.
by fabianlindfors 2y ago
Unfortunately not as Cockroach doesn't support triggers, which is what powers Reshape. We are looking into how to widen support though for our next product, reach out to fabian@reshapedb.com if you'd be interested in something lik
64.
by fabianlindfors 2y ago
These pitfalls are one reasons why I built Reshape [0], which aims to automate zero-downtime schema migrations. I can’t say it avoids all of them but we are working on a new product that would. If you are interested in this space (and Postg
65.
Complex zero-downtime schema migrations in Postgres(fabianlindfors.se)
2 points by fabianlindfors 3y ago|0 comments
66.
Show HN: Reshape – Zero-downtime schema migrations for Postgres(github.com)
2 points by fabianlindfors 3y ago|0 comments
67.
by fabianlindfors 3y ago
> I find the premise of this article (that a small maintenance outage is never acceptable) to be unreasonable for the vast majority of applications developed by the vast majority of developers. Completely agree on this point! Downtime is
68.
Renaming database fields is ureasonably hard(fabianlindfors.se)
1 points by fabianlindfors 3y ago|3 comments
69.
by fabianlindfors 3y ago
The database aspect of this problem is particularly interesting to me. I’ve previously built Reshape [0], a zero-downtime migration tool for Postgres, and am now working on ReshapeDB [1], a full database designed from the ground up to tackl
70.
by fabianlindfors 3y ago
You got it right! I wrote a blog post a few years back about how this technique works for anyone curious: https://fabianlindfors.se/blog/schema-migrations-in-postgres...
71.
by fabianlindfors 3y ago
Congrats to the lovely Xata team on another great launch! I'm the creator of Reshape [0], a similar tool which inspired pgroll, and seeing the concept taken even further is really exciting. [0] https://github.com/fabian
72.
by fabianlindfors 3y ago
Big fan of formalizing state machines and designing backends around them. I’ve been building a similar thing [0] but taking it a step further by enabling async tasks to run in response to transitions. [0] https://github.com/
73.
Show HN: Restate – Build reliable back ends using state machines(github.com)
1 points by fabianlindfors 3y ago|0 comments
74.
by fabianlindfors 3y ago
Probably not exactly what you are thinking of but my project Restate is all about building backends using state machines by saving them and their transitions to the database: https://github.com/fabianlindfors/restate
75.
by fabianlindfors 3y ago
One quality about state machines that I find overlooked is debuggability. Limiting state updates to transitions makes it so easy to debug weird edge cases and race conditions. This upside is perhaps more relevant on the backend though where
76.
Show HN: Restate – Build understandable backends with state machines(github.com)
2 points by fabianlindfors 3y ago|0 comments
77.
Zero-downtime schema migrations for Ruby on Rails(fabianlindfors.se)
1 points by fabianlindfors 4y ago|0 comments
78.
Zero-downtime schema migrations for Ruby on Rails(fabianlindfors.se)
1 points by fabianlindfors 4y ago|0 comments
79.
by fabianlindfors 4y ago
This is precisely what I did for my automated zero-downtime migration tool and it works pretty well: https://github.com/fabianlindfors/reshape . At least for Postgres, simple views like these have almost no overhead as
80.
by fabianlindfors 4y ago
Anybody interested in this subject might also be interested in a tool for Postgres I’ve been working on, Reshape: https://github.com/fabianlindfors/reshape . It aims to fully automate away all the pain and manual steps
81.
by fabianlindfors 5y ago
Nice tool! Shadow tables are quite convenient as they support arbitrary ALTER TABLE statements but they also seem a bit wasteful to me. I'm working on a similar tool called Reshape ( http://github.com/fabianlindfors&#x2F
82.
by fabianlindfors 5y ago
I don't believe Postgres supports temporal tables and as Reshape is Postgres-only, it won't help. The principle behind Reshape might be applicable to temporal tables though but I don't have enough experience with them to say.
83.
by fabianlindfors 5y ago
Thank you! :)
84.
by fabianlindfors 5y ago
That's right! "Simple" views (ones mapping directly to a table) are quite powerful in Postgres and an application interacting with them won't know the difference.
85.
by fabianlindfors 5y ago
This post is absolutely terrific and has been been my main reference for Reshape, an automated, zero-downtime schema migration tool: https://github.com/fabianlindfors/reshape
86.
by fabianlindfors 5y ago
You might also be interested in Reshape, a tool I’ve been working on to automate zero-downtime deployments with Postgres: https://github.com/fabianlindfors/reshape
87.
by fabianlindfors 5y ago
I’m not sure it’s that innovative but thank you!
88.
by fabianlindfors 5y ago
Great article! For anybody interested in this topic, I've been working on a schema migration tool which automates zero-downtime migrations using many of the techniques mentioned: https://github.com/fabianlindfors/r
89.
by fabianlindfors 5y ago
Let me know your experience when you do try it! Eager to iron out bugs. It's designed to be a full tool to handle all schema changes, replacing tools such as the ones you mentioned :)
90.
by fabianlindfors 5y ago
I'm glad you like it! I hope you'll have some project in the future where Reshape can be useful.

More ›