dataClay is a distributed data store that enables applications to store and access objects in the same format they have in memory, and executes object methods within the data store. These two main features accelerate both the development of applications and their execution.
Stable release: dataClay 4.0 - Claystone (June 2024)
Research Lines:
Contact:
support-dataclay [at] bsc [dot] es
License:
BSD License (Version 2.0)
Primary tabs
Highlights
Internal refactor to leverage the asyncio library (along the asynchronous implementation of the gRPC library, i.e. gRPC AsyncIO API). These changes should be retrocompatible, but you can take advantage of the new asynchronous mechanisms by using the homonomous methods in the client API (e.g. a_make_persistent() instead of make_persistent()).
New experimental feature: AlienDataClayObject. See Alien Objects for a detailed explanation.
New microservice: the proxy. This can be used to circumvent NAT networks (e.g. Docker deployments) and also provides a more secure way to access the dataClay services. See Proxy service for more information.
Other changes
Basic support for JWT tokens in the proxy.
Starting the client automatically starts a new thread and an event loop within. This is used internally to handle the asynchronous calls and gRPC clients.
Updates in the orchestration scripts.
Added explicit get_attribute, set_attribute and del_attribute RPC calls on the backend. This is transparent for the applications (read, set and delete of attributes continue to work), but allows the introduction of fine-grain mechanisms on the proxy and also makes the debugging process clearer.
Offering a new Zenoh bridging mechanism (similar to the MQTT one).
Removed the session and password authentication. This feature will be handled by the proxy going forward.
Added healthcheck mechanisms (at the gRPC level) to monitor the status of the dataClay services.