Hein Meling

Merge these ideas into #562 and close this issue (when at proper keyboard)

Related to a revised database architecture… we should consider the [ent framework](https://entgo.io/) which also has some support for gRPC/protobuf. Also there is [EdgeDB](https://www.edgedb.com/) that uses Postgres, but seems to have...

We could also use a tool such as [reviewdog](https://github.com/reviewdog/reviewdog) to add automated review comments to the PRs.

I think the build log should be viewable via the GitHub actions panel, like other systems do, showing only the main things in the PR overview.

As the following shows, the bundle can be a bit big: ```log assets by status 110 KiB [cached] 23 assets assets by status 607 KiB [emitted] asset npm.google-protobuf.d82c031c96e6cb3ae777.bundle.js 232 KiB...

@johningve Could you resolve the conflicts in this PR before I review it?

Have done a quick high-level scan of this PR. My general comment is that the number of methods in the interface is larger than typical Go interfaces. Also, it is...

I'm closing this PR since it goes against the idiomatic Go style of keeping interfaces small, and interfaces are usually not returned from (constructor) functions but instead accepted as input...

Some questions. 1. In the Separate Checkpoint Service approach, who invokes the service? In the PiggyBack approach it is the leader. 2. Could an alternative design be decentralized? Meaning that...

I've looked at the code, and it looks fine to me. But could edit the PR description to provide some more context for this. Do you think we won't need...