Deprecate geored service?

[osmith42]

PyHSS currently has a geored (geographical redundancy) service.

It seems that this is something the database should handle via its replication features. MySQL/MariaDB and PostgreSQL can both do this:

• https://mariadb.com/docs/server/ha-and-performance/standard-replication
• https://dev.mysql.com/doc/refman/9.7/en/replication-howto.html
• https://www.postgresql.org/docs/current/logical-replication.html

@davidkneipp, @nickvsnetworking: what was the motivation to add this to PyHSS and do you think it still makes sense to keep it?

[Takuto88]

My two cents: this mechanism feels fragile to me, since it assumes HTTP requests are a reliable way to transport important data across database boundaries. This isn't meant to discredit the effort - keeping databases in sync across geographical regions is a genuinely hard problem.

I'd rather see users rely on their SRE/DBA teams to handle this at the database level than depend on this service for it. Failures during HTTP requests (e.g. an HSS being temporarily unavailable, or general network issues) can lead to inconsistent database states, and a service that implies it can handle geo-redundancy without actually being able to do so properly is dangerous.