JSFoo 2019

On component architecture, front-end engineering and Developer Experience (DX)

Tickets

What or how not to do in Redis world

Submitted by Aram (@phoenixwizard) via Zainab Bawa (@zainabbawa) on Wednesday, 18 September 2019

Section: Full talk (40 mins) Technical level: Advanced

View proposal in schedule

Abstract

What is Redis? Taking the first line on the website, “Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker”. You’ve been told how amazing Redis is and have seen many people present it as a silver bullet.

In this land of silver bullets, I would like to show you cases where Redis might fall flat on the face. Some things might be laughable and obvious, and I have seen some big teams make these mistakes, and some are going to be less obvious.

Bringing you my Redis failures and experiences.

Outline

What you can expect from this session:

  • Some of the common mistakes and a few stories of people having burnt themselves
  • (Mis) Using redis as a Persistent storage
  • Single thread headaches
  • Where redis screams & then some (Did someone say rate-limiting?)

Requirements

None

Speaker bio

Aram is a full stack developer who has worked on everything from Ruby, Python and NodeJS, to Html, CSS and Angular. He has used Redis in both places where it had to be used and places which he thought would be a good fit (and has successfully burnt himself). Aram has worked with startups writing the first line of code (including Cloudaria which was his own baby) and consulted for some of the more notable Forbes 100 companies building products for scale. Currently, he works at Zoomcar as a Principal Engineer leading the ZAP tech team.

Slides

https://speakerdeck.com/phoenixwizard/redis-anti-patterns

Comments

  • Zainab Bawa (@zainabbawa) Proposer Reviewer 29 days ago

    Thank you for a really nice rehearsal, Aram. Here is the consolidated feedback:

    1. The slides need reorganizing. The pitfalls of Redis had lots of slides whereas the good parts of Redis had fewer slides but much more material.
    2. Pitfalls were anecdotal. Anecdotes are nice. But present the pitfalls with authority. List all the anti-patterns. This will make your slides good reference material for future.
    3. You have to show how to do what you tell us, and show it in the talk itself. Leave out the good parts of Redis. Just talk about the pitfalls.
    4. Refer to the book SQL Antipatterns by Bill Karwin to talk about anti-patterns in your talk.
    5. Add something about Node.js and Redis given that you mention this in your abstract. If not, change your abstract.
    6. What were the ways in which you overcame the challenges from the pitfalls? Explain this.
    7. Attribute sources for when you take material from other sources.

    On the visual aspects of the presentation, the feedback was:

    1. Break the story down into visual cues.
    2. Use larger sized fonts.

    Share the link to your revised slides on 26 September so that we can go over the slides one last time.

Login with Twitter or Google to leave a comment