Aerospike Developer Blog

​

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.

This is the first in a series of blog posts intended to help folks who may be struggling with deployment of an Aerospike database. I'm part of the Aerospike Developer Relations team, but I spend most of my days playing around with websites or writing code samples, and not deploying databases in real-world contexts. I hope that you can follow along with me as I fumble my way through a production build and create a tool that will not only help me with my job, but also help me learn a whole lot more about Aerospike.

Let me make the mistakes so you don't have to! Or do make them, that's cool too.

​

When using the Aerospike Kubernetes Operator, the complexity of configuring a high performance distributed database is abstracted away, making the task of instantiating an Aerospike database incredibly easy. However, even though Kubernetes leads us towards expecting equivalent results regardless of platform, we need to be mindful of the peculiarities of individual frameworks, particularly if we are repeatedly iterating processes. ​ This article focuses on AWS EKS provisioned storage which is dynamically created when using the Aerospike Kubernetes Operator. Ensuring that storage has been fully deleted and other redundant resources removed is a necessary housekeeping step if you are to avoid unwelcome AWS charges. ​

Queries, scans, indexes, pagination, and parallelism are common concepts in databases, but each database differs in specifics. It is vital to understand the specifics in order to get the most out of a database. In Aerospike, queries and indexes play a key role in realizing its speed-at-scale objective. The goal of this post is to help developers better understand the Aerospike capabilities in these areas.

Welcome to the Aerospike Standup. Here are some highlights:

We released Aerospike SQL Powered by Starburst 1.1.0 that supports Starburst Enterprise Platform (SEP), "a fully supported, enterprise-grade distribution of Trino that adds integrations, improves performance, provides security, and makes it easy to deploy, configure, and manage your clusters."