@getanthill/datastore
Advanced tools
getanthill Datastore
This project aims to help developers deploying state-of-the-art
Event-Source data models in a unified and standardized way. The
Datastore is composed of several parts:
The RESTful API is fully compliant Open API 3.0. It is exposing standardized routes for models managed by the Datastore such as create, update, etc.
Administrators can access routes dedicated to the Datastore
administration on /api/admin once the environment variable flag
FEATURE_API_ADMIN=true.
The SDK is a simple HTTP client helping developers to consume the Datastore APIs from the code. The SDK is for now only available at a low level and in Javascript.
Because the API is Open API 3.0 compliant, any code generator can be used to get a client in your prefered language:
The Backoffice is a User Interface to manage data in your
Datastore. To activate this feature, you must set the
environment variable flag FEATURE_BACKOFFICE=true.
gotoDocumentation
FAQs
Event-Sourced Datastore
The npm package @getanthill/datastore receives a total of 164 weekly downloads. As such, @getanthill/datastore popularity was classified as not popular.
We found that @getanthill/datastore demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.