Aerospike Developer Blog

In this article we focus on establishing connectivity between 2 Aerospike clusters. The goal is to use Aerospike's Cross Data Center Replication feature ( XDR ) to seamlessly send data from a source cluster to a destination cluster. The source cluster needs network visibility of all Aerospike service ports in the remote cluster, and this can present problems, particularly in a Kubernetes environment. Placing a proxy server in front of the private Kubernetes destination cluster can overcome this problem and achieve the desired goal. To demonstrate the solution we start by installing the Kubernetes Operator that will schedule our source and destination databases. In this example, we set up our replication in one direction. Aerospike is capable of supporting 'master/master' replication and provides a conflict resolution mechanism in the event of update clashes. This too could be supported using the XDR proxy.

While it is possible to process a data set using a large number of parallel streams, a higher degree of parallelism may not be necessarily optimal or even possible. This article explores how to think about parallelism, and discusses many bottlenecks that limit the level of parallelism. It also highlights the need to perform measurements in the target setup due to many factors that cannot be easily quantified.

Welcome to the Aerospike Standup. Here are some highlights:

New hotfix releases to Aerospike Database 6.2, 6.1, 6.0, and 5.7 are available. Follow the link in the Releases section for details. Note the Aerospike REST Client is now renamed more accurately as Aerospike REST Gateway.

Aerospike provides several mechanisms for accessing large data sets over parallel streams to match worker throughput in parallel computations. This article explains the key mechanisms, and describes specific schemes for defining data splits and a framework for testing them.

​

In this article we focus on side-by-side block and filesystem requests using Kubernetes.​ The driver for this is it will allow us to deploy Aerospike using Aerospike's all flash mode.

Storing database values on a raw block device with index information on file can bring significant cost reductions, especially when considering use cases for Aerospike’s All-Flash. To support such a workload, you can configure Aerospike to use NVMe Flash drives as the primary index store.

Welcome to the Aerospike Standup. Here are some highlights:

We released Aerospike Database 6.2 with support for 64-bit ARM processors compatible with the ARMv8.2-A instruction set (Neoverse N1 microarchitecture), such as AWS Graviton2 processors. This augments support for 64-bit Intel/AMD processors compatible with x86-64-v2 microarchitectures.

• Check out the blog post Aerospike Database 6.2 on Graviton: another step in providing the best cost-performance ratio.
• Aerolab, the Lab tool for spinning up Aerospike development and testing clusters on Docker or in AWS, now supports the M1 Mac processor with 6.2!
• Note the breaking changes in Server 6.2: Debian 9 support is removed, and the ARM64 version does not support LuaJit. Follow the link in the Releases section for the release notes.

The REST Gateway provides you with a well known interface to your Aerospike Database, and a Swiss army knife-like solution to a variety of architectural problems where you might not want to integrate a full fledged Aerospike client into every application.

Introduction​

MQTT (Message Queuing Telemetry Transport) is a widely used messaging protocol for the Internet of Things (IoT). It is ideal for communicating with small remote devices with limited power and network bandwidth. MQTT is used in a wide variety of industries, such as automotive, manufacturing, telecommunications, oil and gas.

Aerospike Database is deployed by large-scale real-time applications in a wide range of verticals. Businesses need “as it happens” visibility over these systems - sometimes in near-real time - via notifications, ad-hoc queries, dashboards, and reports.

SQL is broadly used as a data access language for analytics, and Trino provides a powerful engine for SQL access to multiple data sources. Aerospike Trino Connector enables SQL access to Aerospike data through Trino, and more broadly, allows Aerospike to be used to expand fast analytics data accessible from Trino.

Welcome to the Aerospike Standup. Here are some highlights:

Coming up on November 15, 2022 in Chicago is the meetup with Chicago PostgresSQL Meetup group. Topic: Building a Fast Document Store at Scale with SQL Access. Register now!

In Las Vegas on November 28 - December 2, 2022, visit the Aerospike Expo Booth #3835 at AWS re:Invent for a demo of Aerospike Cloud on AWS.