PgHero VS relic

I am using https://github.com/ankane/pghero/ and this is one of its features with GUI

I use either PgHero or Rails PG Extras on every project

There are tools available which can look at your Postgres logs and tell you if you need to add indexes, I've used https://github.com/ankane/pghero before and it seems decent.

https://github.com/ankane/pghero (open source equivalent to pganalyze)

- [pghero](https://github.com/ankane/pghero)

pghero

If you are using PostgreSQL you can enable logging of slow queries and connect to the server with pghero (https://github.com/ankane/pghero) and check top queries by the number of requests and total usage time. Also, you can just enable logging of queries in Django, and on each request, you will have a list of queries on development, sometimes it's just a missing select_related of prefetch_related to increase performance, or you need to create a complex index.

If you are using rails, pghero is a great gem to get better visibility on your Postgres performance

https://github.com/ankane/pghero

I know others can answer this better but we use a combination of PgHero and logging of slow queries trough jOOQ.

I've been tooling around with "Tuple Database", which claims to be FoundationDB for the frontend (by the original dev of Notion).

https://github.com/ccorcos/tuple-database/

I have found it conceptually similar to Relic or Datascript, but with strong preformance guarantees - something Relic considers a potential issue. It also solves the problem of using reactive queries to trigger things like popups and fullscreen requests, which must be run in the same event loop as user input.

https://github.com/wotbrew/relic

As an alternative to datascript you might be interested to try https://github.com/wotbrew/relic which does materialized views of queries with incremental maintenance.

I came across this after seeing relic[0] submitted the other day and thought it was pretty interesting.

I've been into CRDTs for a while and have started wondering about generic mechanisms for distributed data. This lead me to read a lot more about the Relational Model of data and eventually to the Event Calculus.

What's interesting to me is that these things end up feeling a lot like CRDTs[1] or Event Sourcing. I haven't quite finished pulling on these threads but the relic link was a timely read considering!

I really liked the first half of this paper and the Authors categorization of complexity. However the second half fell a bit short for me. It seems they made the same mistake as many other people (SQL != Relational) and their idea of Feeders and Observers seems a bit more like an escape hatch than an elegant method for interfacing with the outside would.

[0] https://github.com/wotbrew/relic

I have recently cut the first alpha release of relic that I'm happy to share: https://github.com/wotbrew/relic.