Sorry, we didn't make it clear on the website. We only build and generate the REST API, so you can only focus on the frontend side. Anyway, Thanks, I appreciate your taking the time to write.
Sorry, We didn't make it clear on the website. In short, We build and generate REST API for you, so you can focus on building on the frontend side. Thanks, I appreciate your taking the time to write.
Sorry, We didn't make it clear on the website. In short, We build and generate REST APIfor you, so you can focus on building on the frontend side. Thanks, I appreciate your taking the time to write.
Yes, I've seen them, We try to be different, keep improving and adding more features to make the product even more valuable to people. Thanks, I appreciate your taking the time to write.
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.