outstatic VS temporal_tables

Shameless plug, but depending on your needs check out https://Outstatic.com

Hey HN,

These claims that op has made have been found to be false. His project uses an Open MIT license, and I forked it like a good OSS community member does.

The main dealer breaker for me not using his code directly within my project was a serious GDPR and data privacy violation that I found on the surface of OP’s code.

https://github.com/avitorio/outstatic/blob/d440f8f53ee559fb3...

There is no disclaimers or privacy polices within OP’s website, project, or readers that say he is collecting analytics data, including sensitive GitHub project details.

Some of my users and customers require ISO2700 and SOC2 compliant solutions, and this was a huge red flag to us.

I contacted OP about it, and other security issues, but he blew me off and turned to trashing me online like this.

What do you think?

Check the project out at: https://Outstatic.com

In case you want to check the repo: https://github.com/avitorio/outstatic

There is also the temporal_tables extension.

[0] https://github.com/arkhipov/temporal_tables

- https://github.com/arkhipov/temporal_tables

I haven't used any of these but I work on https://xtdb.com which is also implementing SQL:2011's temporal features :)

It seems like PG has this extension here anyone ever use it?

You could look at that or ask me questions about it (disclaimer, I am the author). Also there is https://github.com/arkhipov/temporal_tables/

All good. Note there is also https://github.com/arkhipov/temporal_tables/ (which is also type 4 as a postgres extension - pretty similar to what ebean orm is doing)

The Temporal Tables Postgres extension works well. https://github.com/arkhipov/temporal_tables

If you're doing this across regions, you really really should reconsider. If you're doing it in the same data center you might be able to get away with it (but then I'm not sure why you're doing it in the first place, if the system fits in one DC then you probably can just scale up). It might be worth considering a sharded & passively combined approach -- i.e. every country has it's own data, and there's some huge public schema which consists of all the data that is drip fed in to materialized views or tables at regular intervals. You could also combine this with temporal_tables to get a very delayed but theoretically time-consistent (well, aside from clock skew across regions of course...) view of your DB to query... Really depends on the use case.

One of postgres's most underrated features. RLS is amazing, can be unseen/basically work silently if your programming language-side tools are good enough, and is documented well (like everything else):

https://www.postgresql.org/docs/current/ddl-rowsecurity.html

But the power of PG is that it doesn't stop there, if you combine this with a plugin like temporal_tables and you can segment by user and time:

https://github.com/arkhipov/temporal_tables

All of this mostly unknown to the thing that's accessing the DB. If that's not enough for you, why not add some auditing with pgaudit:

https://www.pgaudit.org/#section_three

I think it might not actually be hyperbole to say that Postgres is the greatest RDBMS database that has ever existed.