|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Federated Tables API (ranked 286 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Federated_Tables_API_55db471f_653e_4c48_9bb4_2bcd3888bfa1_yaml.yamlGENERAL INFORMATION
Warning: Federated Tables is in BETA stage and the API might change or have limited support.
Introduction
A Federated Table is a PostgreSQL Foreign Data Wrapper to a remote server, allowing us to perform live queries to a remote database. Think of it as a virtual table that looks like a regular sync table in CARTO — but when used, makes the queries you perform in CARTO travel to the remote database and get executed there.
Typically, the use cases for Federated Tables include having frequently changing data that you join with other tables in CARTO. Having a large amount of data that is dificult to sync with CARTO but that you only need to query distinct parts of, like in the case of time-series databases. Even when you want to leverage the scalability or low latency of your cloud database from within the CARTO ecosystem.
The API allows you to register remote databases, then you can browse remote schemas and tables to register those you want to use with CARTO as a regular table
...
Contact
- Name: Have you found an error? Github issues
- Contact API maintainers
SECURITY 4/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API7:2023
PERFORMANCE 2/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 469 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 2/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 3.0.0 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 4/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!