[alfaa]

We built this initially only to turn the database into API, after ask to users, we found that some people need more than just accessing the database. For example, they want to send notifications to Slack/Telegram when an event happens in the database, or they need to upload a file to the cloud storage, then put the information to their database. That's why we put another service, although they also have an API. Our goal is to make their needs covered in a single platform. Currently, we are working on the "API Workflow" to simplify the process above, so they don't need to write multiple API request in their app.

what happens when we hit rate limit on the upstream service? We will just return the response from the upstream service? And user will get rate limit error. We plan to cache the API calls (can be configured by user) to avoid making repetitive API calls to the upstream.

Anyway, Thank you. We value and respect your opinion. It means a lot for us to make the project even more valuable to people.

[debarshri]

API workflow is a solved problem. Have you looked at zapier?

The thing is if you return the response of upstream service, it is jargon for me because I did not use the upstream's service directly.

Caching API calls might be a bad idea as it might create inconsistent data. Just saying, it is a hard problem in general. Abstractions are hard problem in general.