xk6 VS Redis

Recently, k6 started supporting k6 extensions to extend k6 capabilities for other cases required by the community. The community has already built plenty of extensions. k6 extensions are written in Go, and many of them are reusing existing Go libraries.

Previously, I have covered an article on Load Testing SQL Databases with k6. For your information, from k6 version 0.29.0 onwards, you can write a k6 Go extension and build your own k6 binaries. This comes in handy as you can use a single framework for load testing different protocols, such as ZMTQ, SQL, Avro, MLLP, etc.

First of all, you need to install redis on your machine : Visit http://redis.io and setup redis-server.

What version are you running? 6.2.7 & 7.0rc2 included a fix for sentinels not refreshing IP addresses - make sure you also have resolve-hostnames on.

celery beat coupled with redis,

Redis

So, is JR yet another faking library written in Go? Yes and no. JR indeed implements most of the APIs in fakerjs and Go fake it, but it's also able to stream data directly to stdout, Kafka, Redis and more (Elastic and MongoDB coming). JR can talk directly to Confluent Schema Registry, manage json-schema and Avro schemas, easily maintain coherence and referential integrity. If you need more than what is OOTB in JR, you can also easily pipe your data streams to other cli tools like kcat thanks to its flexibility.

I am a fan of Gearman to schedule and dispatch distributed jobs, Redis as a collaborative blackboard, and GlusterFS to share models across multiple systems and make bulk data available across the entire system (usually referenced in the blackboard as a pathname).

I did however learn that LOLWUT is a command, https://github.com/redis/redis/blob/unstable/src/lolwut.c

Depending how much resources your system has, you can look into redis as a central location for all the data, services can subscribe etc.

Redis - A store to facilitate the expiration of tokens, etc.

A server without any persistence is quite limited in what it can do. In part 2 we will cover adding redis to our application, and how to iterate with a fast local workflow that's not possible with other platforms.