Welcome to the Aerospike standup, a newsletter written by developers for developers, that brings together blog posts, questions from the community, documentation, releases and events, written by the Aerospike team.
In this post, we will show how Aerospike features enable Microservices architecture. Specifically, we will see how separation, coordination, and consistency among services is supported.
This is the second in a series of articles describing a simplified example of near real-time Ad Campaign reporting on a fixed set of campaign dimensions usually displayed for analysis in a user interface.
How to implement transactional semantics in your Aerospike application. Certain situations have to be handled differently from traditional databases that you may be familiar with because of the single record scope of Aerospike transactions and certain cluster transitions.
This article is Part 1 of a series of articles describing a very simplified solution for near real-time campaign reporting, that is campaign reporting on a fixed set of dimensions and usually displayed for analysis in a user interface.
Aerospike is a distributed key value database, designed to support high levels of throughput, with minimal latency, at scale. Aerospike is optimised for use with flash based storage enabling it to achieve world class performance with best in class density and cost.
Rethinking a ScyllaDB Benchmark as an Aerospike Developer