4 ms·
Unrelated to the article, but I gotta say I just learned about Sequin from this link, and it seems very cool! But, I can't think of a use-case for it. Can you p
by brap 3y ago
Unrelated to the article, but I gotta say I just learned about Sequin from this link, and it seems very cool! But, I can't think of a use-case for it. Can you please explain the value-add?
- _acco 3y agoHey there, author here. We help our customers build their integrations faster/easier by syncing API data with Postgres tables. Because your API data is in Postgres, you can query it exactly how you like. You're not limited by the API's supported query params, batch sizes, or rate limits. You can use SQL or your ORM. This also means you don't need to learn all the API's quirks. And every API we support has the same interface. (Which will become more valuable as we add more APIs!) So, the value is less code and simpler code.
- brap 3y agoInteresting, thanks. Do you manage the DB yourself or do you sync it to customers' existing DBs? Does this play nicely with pg_graphq?
- _acco 3y agoWe offer a demo Postgres instance for getting up and running. You can move the sync to your db when you're ready for production. Therefore, should be compatible with extensions like `pg_graphql` (can't think of customers using that extension, but we have quite a few using Hasura). Any other questions, feel free to email: anthony@[domain]