Welcome to the Aerospike Standup. Here are some highlights:
We are restarting developer meetups! The first one is scheduled on Tuesday, July 19th in our Mountain View office. Join us if you can and learn from experts at PayPal about robust and scalable monitoring of over 2000 Aerospike nodes as well as the high level architecture of their AI/ML-based real-time fraud detection and prevention system.
We released Aerospike Monitoring version 2.0.0 adding support for many new Aerospike 6.0 metrics in the Grafana dashboards. (Note that the 2.0.0 Grafana dashboards are not backwards compatible with Aerospike servers older than 6.0.0.0.) We also released Aerospike Prometheus exporter version 1.6.0 to support metrics added in Aerospike server 6.0.
The blog post Are Graph Databases Finally Ready for Prime Time? announces the Firefly Alpha Program, the code name for Aerospike’s graph database offering. Firefly combines Aerospike Database with Apache TinkerPop™. If you would like to sign up, please reach out at firefly-alpha@aerospike.com.
The article Data Modeling for Speed At Scale (Part 2) continues where last month's post left off, and describes how applications can optimize speed and scale by leveraging Collection Data Types (CDTs).
See below for details on the blog posts, releases, questions from the community, and events collected from this past month.
Upcoming Events
New Blog Posts
Data Modeling for Speed At Scale (Part 2)
by Neel Phadnis
Are Graph Databases Finally Ready for Prime Time?
by Ishaan Biswas
Releases
Java Client
Go Client
Node.js Client
C Client
Ruby Client
Connect for Spark
Monitoring Stack
Prometheus Exporter
Tools
Questions From the Community
Nodes in different clusters on the same subnet with mesh configuration form ONE cluster
Namespace configuration in Aerospike 5 - namespace vs dc contexts
Interaction of List operation (getByValue) and more complex data types
In which situation one record may have multi generations in storage
What is the lowest compatible Aerospike Enterprise Server version for Java client 5.1.11?
Can we change the time one node take to join cluster after restart?
Atomic increment via operate command using java client (5.1.5.1) fails