Adding a Clarabase API to your projects
Last updated
Last updated
Clarabase is simple to integrate into your new and existing projects. The guiding principle of using a Clarabase API is to create a wrapper and have other parts of your code depend on the interface exposed by your wrapper (this is known as the Dependency Inversion SOLID principle). We strongly recommend using one of the sdks generated by Clarabase as they structure your code for you to do the following:
Seamlessly handle authentication between your server and Clarabase
Adds default retry and error handling
Abstracts the data management portion while making it easy to change if you need to do so in the future
Note: Clarabase is not a Backend-and-as-Service platform. It's meant to be used in "server-to-server" contexts, not "client-to-server" as a BaaS platform like Firebase or Supabase would. But it makes a lot of the data manipulation code you would normally write easier to work with.
BaaS platforms provide a lot functionality such as Authentication, Storage, Compute, and Database abstractions. This is often at the cost of flexibility and your ability to adapt your codebase to the changes within your business or use case. This is referred to as "vendor lock-in".
Often times, these platforms will encourage making db calls directly from your client-side, which is an antipattern and makes it very difficult for you to change things in the future.
Clarabase's philosophy is that your entire backend should not be in the hands of a 3rd party vendor, but rather that vendor should provide high level abstractions that make initial and long-term development easier. You can use Clarabase for a small feature or for all the resources your backend needs to control.
