How Redis Founder Salvatore Sanfilippo Defied Database Conventions

Salvatore Sanfilippo (antirez) started creating Redis in 2009 as a hobbyist with virtually no professional database experience, and his lack of conventional background allowed him to break many so‑called “iron rules” of database engineering.

Today Redis is one of the world’s most popular databases, powering services at Uber, Instacart, Slack, Hulu, Twitter, Instagram and many others, even though most products do not display a “Redis inside” label.

Sanfilippo does not prescribe how Redis should be used; he believes application developers are best positioned to decide its role.

No DBA Expertise Required

Before Redis, Sanfilippo was already known in the security field, creating the network‑security tool hping, the Idle Scan port‑scanning technique, the Visitors web‑log analyzer, the Jim Tcl interpreter, and several hardware drivers.

He also ran a real‑time analytics service called lloogg.com, initially trying to power it with MySQL, only to discover that the hardware cost for serving ten thousand users far exceeded the revenue.

He realized that storing workloads in memory and trimming lists to a fixed length could not be efficiently achieved with a relational database, which led him to start building Redis.

Redis was not assembled from existing database features; instead, Sanfilippo re‑thought the underlying data model and created an in‑memory NoSQL database that serves both as a data store and a cache, deliberately breaking traditional database “iron rules”.

Database purists initially criticized Redis for keeping data in memory, using the fork system call for persistence, and for its Lua scripting approach, but they lacked insight into how future databases could be built.

Making Friends and Influencing Others

Despite criticism, Sanfilippo continued to innovate freely, driven by his belief in open‑source collaboration. He has been involved with open‑source since he installed Slackware at age 18, which included a C compiler, launching his software development career.

For him, open source is more than a licensing model; it is a human activity that tells stories, and he travels to share the Redis story.

Redis first gained traction in startup communities and later in mature enterprises, forming a vibrant community where, after ten years, its core will be the product of many contributors.

Personal Choices

Over the past decade Sanfilippo faced pressure about Redis’s success and funding, but the database’s growth alleviated those concerns, allowing him to join Redis Labs full‑time.

He does not dictate how Redis should be used; developers decide its purpose—whether as a primary database, an index for another store, a smart cache, a message queue, etc.

Sanfilippo provides a set of components that developers can creatively assemble, enabling Redis to be easily modified for unforeseen tasks.

He does not see himself as an authority figure; he prefers designing new things and turning them into code, leaving the choice of “king or queen” to the developers who use Redis.