The database firm Aerospike has introduced the newest model of its Kubernetes Operator with new options that enhance backup and scalability.
The Aerospike Kubernetes Operator (AKO) permits customers to simplify administration and monitoring of their Aerospike databases.
AKO 3.4 incorporates the not too long ago launched Aerospike Backup Service (ABS), which permits for simple administration of backup jobs throughout Aerospike clusters. ABS runs on a VM or Docker container and offers a set of REST API endpoints for backing up and restoring database clusters. It permits for each full and incremental backups, helps the creation of various backup insurance policies and schedules, and gives usability enhancements over the standard asbackup and asrestore command line instruments.
Moreover, with this launch, the corporate has doubled the default useful resource limits to raised assist prospects needing to scale.
One other new functionality in AKO 3.4 is the power to pause all AKO operations after which simply resume them when prepared. In keeping with Aerospike, that is helpful for triaging incidents.
This model additionally helps Aerospike 7.2, which was launched in early October and introduced with it new capabilities like Lively Rack, a multi-zone deployment possibility that cuts the prices of interzone information transfers.
Different options of observe on this launch embody the power to set off heat and chilly restarts to Aeropsike clusters and integration of the Aerospike Monitoring Stack with AKO.