[–] typingmonkey 4y ago ↗ Is it possible to also expose a websocket that emits changes? [–] killingtime74 4y ago ↗ Hasura has this https://hasura.io/docs/latest/graphql/core/databases/postgre...
[–] killingtime74 4y ago ↗ Hasura has this https://hasura.io/docs/latest/graphql/core/databases/postgre...
[–] misterpurple45 4y ago ↗ This is very seductive, but what happens when I need to refactor the database? Do all my API consumers just have to deal with a new interface? [–] lf-non 4y ago ↗ Yes, A popular convention when using such tools is to use views for any tables that may change, and then treat those views as public interface.So, when you refactor the underlying, you can also update your view definition so that the interface remains the same. [–] [dead] redis_mlc 4y ago ↗ Correct, hence GraphQL, which is more adaptable since it can be used in a higher-level way than columns.
[–] lf-non 4y ago ↗ Yes, A popular convention when using such tools is to use views for any tables that may change, and then treat those views as public interface.So, when you refactor the underlying, you can also update your view definition so that the interface remains the same.
[–] [dead] redis_mlc 4y ago ↗ Correct, hence GraphQL, which is more adaptable since it can be used in a higher-level way than columns.
6 comments
[ 3.0 ms ] story [ 21.8 ms ] threadSo, when you refactor the underlying, you can also update your view definition so that the interface remains the same.