Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
1–10 of 25 posts
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#2seems like sequor.dev (docs site) is down..
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#3> Fuses API execution with SQL logic to provide an open, flexible platform (…)
But there’s a gigantic multi line string in your yaml. Full of Python.
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#4seems like sequor.dev (docs site) is down..
Thank you for letting me know! I'm not seeing any issues on my end - both https://docs.sequor.dev/ and https://sequor.dev/ are loading fine for me. This might be a temporary issue or could be related to your location/network. Try to refresh it. Let me know if you're still having trouble!
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#5>> intuitive YAML-based workflow definition.
in my opinion, there is very little intuitive in a mix of yaml + templating engine, sql, python, and custom DSL logic
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#6> Fuses API execution with SQL logic to provide an open, flexible platform (…) But there’s a gigantic multi line string in your yaml. Full of Python.
The Python here is doing exactly what it should - extracting nested data and flattening it into proper relational tables. Most of the 'Python' is actually just the return statement defining table schemas. The schema can be defined separately and reused across API calls. With such reuse the Python part would be really compact. This is the right balance between declarative config and the flexibility needed for real-world API responses. I can confirm it from my experience developing many integrations with Sequor - this approach handles real-world complexity much better than pure declarative tools.
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#7This looks quite similar to Arazzo: https://github.com/OAI/Arazzo-Specification/
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#8>> intuitive YAML-based workflow definition. in my opinion, there is very little intuitive in a mix of yaml + templating engine, sql, python, and custom DSL logic
Fair point - 'intuitive' is subjective and depends on your background. Let me explain where each technology fits: HTTP request configuration (URL, headers, parameters) is pretty intuitive and similar to Postman that most people know. Python is used mainly for response parsing - without a general-purpose language in this place it would be very limiting. Templating is mainly for variable substitution, familiar to anyone using frameworks like dbt. And SQL stays separate from Python - they're not mixed together.
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#9seems like sequor.dev (docs site) is down..
Thank you for letting me know! I'm not seeing any issues on my end - both https://docs.sequor.dev/ and https://sequor.dev/ are loading fine for me. This might be a temporary issue or could be related to your location/network. Try to refresh it. Let me know if you're still having trouble!
well, that's one way of learning that my company is now blocking some traffic on the vpn... works fine when I drop off the VPN, thanks.
Re: Build API integrations with SQL and YAML – no SaaS lock-in, no drag-and-drop UIs
#10The request / data fetching is interesting in how "easy" it is to write. I did basic perusal of the examples, but I'd be interested to see what it looks like with rate-limited endpoints and concurrent requests.
Another tangentially related project is https://steampipe.io/ though it is for exposing APIs via Postgres tables and the clients are written using Go code and shared through a marketplace.