Introduction In these articles, I'll be exploring the use of beyond storing data. In this particular one, I'll be using it as a messaging paradigm. Redis key-value Publish/Subcribe About the Publish/Subcribe pattern I'm pretty sure that if you've been learning backend development, you already heard of this messaging pattern. The general idea that I get from this pattern it's as follows. The of the message, let's call it , needs to send a message, or several of them, to a or a group of them, let's call these guys . This guy, is an anti-social, he doesn't care who is in the other end, he  wants to reach out his without interacting directly with them. I love this guy 😎! sender Publisher receiver Subscribers Publisher subscribers While the ,  want to know about certain contents, so he subscribes to some of his interest, and he doesn't care either from whom comes the message, he's hunger for content about this topic. subscriber topics How is this even possible? 🤔... Yep, I bet you already figure it out, if they cannot communicate directly, they use a , let's call this guy a . Let me clarify that this is not the only way they can communicate, so this is not the only to use a more formal name. As an example of another way of pattern that doesn't use a , check out it's pretty interesting I didn't know about this, but let's just focus on the . middle man broker topology Pub/Sub broker Data Distribution Service broker Now that you get a broad idea of how this pattern works, well a silly idea of how it works. You may be wondering where is in all this. Well, can also be used as a between these two anti-socials, between the and the . Let's see Redis in action. Redis Redis middle man Publisher Subscriber Prerequisites Yes, of course, Redis. You could download it directly from their page ( ). Just 2.3 mgb, and reading the Readme file, would be enough. redis download (Optional) A redis client in a programming language of your preference, I've used in Python, , in Go and in C . The best documentation is with the Python guys, in my opinion of course, but the three of them are pretty straightforward, with many examples on their source code. Looking at the test folder, could also give you an idea of how to use the library. aioredis go-redis/redis hiredis Compiling redis When you downloaded the source code from the previous link, decompress the file and put you in the terminal inside this folder, that at the writing of this tutorial the version of redis is . When you are in there,  run this: redis-6.2.4 make The magic of GNU Makefiles. After the compilation is done, it should show you something like this: Hint: It's a good idea to run 'make test' ;) A valid hint, you should, it  takes a lot of time, redis is heavily tested. No code, just redis-server and redis-cli After the compilation you inside the folder you should have two binary files, well more than two, but we just care about these two. One is the and the , the names are self-explanatory. Open three terminal on this path, and run: src redis-server redis-cli ./redis-server and ./redis-cli in the other two. You will notice that redis is extremely fast. In the instances, we are going to write out commands that goes to the . redis-cli redis-server Now let's say a want to get messages related to a or , you could imagine something in your head like this: subscriber topic channel SUBSCRIBE fake_news Well it's like that 👀, yep, not lying to you. But wait, and the ? You got me, if you just make this you won't get anything until the decide to publish something on this particular , . Now in the other terminal running the other instance of ,  you should run this one publisher publisher topic fake_news redis-cli PUBLISH fake_news "you won't be bald at all man" If you keep an eye on the other instance that got the , you will see that it receives this message. Take a look, the publisher didn't specify anything about the , that's right, because he doesn't care he just wants to pass his " ". Subscriber subscriber fake news Now think calmly, why is this pattern so amazing, write down your conclusion, so you don't forget them later when you actually need to use it. Using hiredis #include <stdio.h>
#include <hiredis/hiredis.h>

int main(int argc, char *argv[])
{
    redisContext *ctx = NULL;
    redisReply *reply = NULL;
    
    /*initialize redis context*/
    ctx = redisContext("127.0.0.1", 6379);
    if(!ctx || ctx->err) {
        if(ctx){
            fprintf(stderr, "ERROR: %s", ctx->err);
            redisFree(ctx);
            return 1;
        }   
        else {
            fprintf(stderr, "Couldn't allocate redis context");
            return 1;
        }    
    }
    //now to send a command
    reply = redisCommand(ctx, "SUBSCRIBE fake_news");
    printf("EXTRA EXTRA: %s", reply->str);
    
    //cleaning the mess
    freeReplyObject(reply);
    redisFree(ctx);
    return 0;
} For the would be very similar, you need to change with the Publisher's command. Publisher redisCommand Even in is not so much code, of course there's a library for that, but that's the point you don't need to reinvent the wheel. C Conclusion It seems that redis is more than just a "key-value" database, or at least it can be used for other purposes as well. Next time will be using . Redis Streams Bibliography Official website Redis Pub/Sub Pub/Sub paradigm hiredis documentation

Keep

Read My Stories

Too Long; Didn't Read

Get free API security automated scan in minutes

Exploring Redis: How the Publish/Subscribe Pattern Works

Too Long; Didn't Read

Company Mentioned

@gulolio

RELATED STORIES