Re:A database for 2022
by throwdbaaway on Saturday April 02, 2022 @09:57AM
(#30888328)
Sounds like postgres listen/notify could be viable for your high-read-low-write use case? Or it is not scalable enough for the fleet size?
That's still all your infrastructure components calling out to an external service on every read --- and for what advantage?
This isn't an app server; it's an infrastructure component, running (I don't know about Tailscale here, but we use SQLite in similar uses cases) on potentially hundreds or thousands of machines.
Re:A database for 2022
by throwdbaaway on Saturday April 02, 2022 @08:52PM
(#30893148)
No, you don't need to make any network call on every read with listen/notify. It will essentially be a local cache, working the same way as etcd watcher, using one postgres connection per machine.
Re:A database for 2022
by statictype on Saturday April 02, 2022 @12:01AM
(#30885763)
Makes sense once you think of Tailscale as an infrastructure-level service and not just an app. Thanks
We use Postgres! It's the backing state for our API, and an important source of truth in our architecture. Postgres is a great way of serving a GraphQL API. It is not necessarily a good way to back an infrastructure service.