How I select the optimal AWS instance type for running Aerospike
One of the most common conversations I have when providing consulting services for Aerospike customers running on AWS is about how to select the optimal AWS instance type.
When it comes to running production Aerospike workloads at scale on AWS I generally only look at a this short list of instance families:
In the Enterprise Database Security session I presented at Aerospike Summit 2020 I gave an overview of authentication and authorization with Aerospike Enterprise.
To provide context, refer to the following diagram depicting an Aerospike deployment.
Serializing and compressing data client-side before storing it in a back-end database is a common pattern. I run into this frequently in my work with Aerospike customers, typically in the form of protocol buffers (protobuf) or gzipped JSON. After all, who doesn’t want to reduce network bandwidth and storage?
However, unless the use case is a dumb-simple get/put cache, you may be trading off some powerful Aerospike functionality for very little gain — if any.
Some of the benefits of serializing and compressing objects client-side include the following:
Architect, software engineer, and general tinkerer.