Three winners. Three unique applications – and plenty of innovation in real-time application performance.
The 2022 Redis Hackathon launched in collaboration with DEV in August 2022. Redis called upon the dev.to community’s most engaged, creative minds to build applications using Redis Enterprise’s many functions, modules, and products. Redis’ strengths go well beyond caching, so the contest challenged the community to showcase what’s possible in building applications backed by enterprise-grade performance.
Download our e-book Enterprise Caching: Strategies for Optimizing App Performance.
We received 91 valid submissions in four project categories:
The Redis Hackathon selected five grand prize winners, 20 runners-up, and 25 extra participants that included a video of five minutes in length or longer with their submission.
All of them achieved remarkable things, so we asked three of our grand prize winners to share the technical details of their projects, including their plans to expand their applications with Redis.
Hi, I’m Subham Sahu, an engineer who loves exploring and building things. I’m a recent undergrad from the Indian Institute of Technology Ropar.
What does OneSocial do?
It’s an app for creators and their audiences. With OneSocial, anyone can share their thoughts on their blog, manage an active newsletter, organize events, and make their content more discoverable. Want more? One can sell digital offerings, such as notion templates, design illustrations, or stock images, as well as services like video consultation, mock interviews, resume reviews, etc
How will OneSocial make creators/influencers’ lives easier?
Creators have to use multiple websites and social platforms to run their businesses. As a result, creators’ audiences are scattered across many social media channels. To ensure that the latest announcement reaches them, the creator has to post the same thing repeatedly on various websites. It is time-consuming, cumbersome, and possibly destructive to one’s brand, as asking loyal followers to subscribe to your content on multiple platforms could be a big ask.
The aim of OneSocial is to build a single platform that provides creators with all the necessary tools and functions from top to bottom, so they can have their entire audience under a single roof.
Techie details: How did you build your application?
The communication between server-to-server, server-to-client, and client-to-server is done via GraphQL. The front end is built using Next.js, and the back end uses Express (Node.js library). We’re using Cloudinary and Google Cloud Storage to store images and files securely.
Stripe powers the payments module, while Redis queue serves as the notifications system. The chat module uses Redis Streams, WebSockets, and GraphQL subscriptions to keep persistent connections and deliver messages instantly.
The data is stored as Redis JSON, and we use the Redis-OM Node.JS library to interact with the database. All major fields and attributes are indexed or sorted for best performance based on the design requirements. We’re also using RediSearch to perform a full-text search on the data in Redis. Finally, we’re using Redis Streams to publish and subscribe to events across multiple services.
Hello. I’m Nabil, a contract developer based in Nigeria.
Pic-Placeholder is a stylish image placeholder with more than 500 images in six categories: animals, cats, dogs, houses, landscapes, and people.
What was the lightbulb moment that led to Pic-Placeholder?
When I heard about the Redis hackathon, I didn’t know what to build, but I still wanted to participate. I’d been hearing about Redis for a while but never had a chance to work with it.
I was helping a friend with a real estate app, and we wanted to use lorem picsum as a base for placeholder images, but we couldn’t because it was too generic, so I ended up building my own.
What can Pic-Placeholder users hope to accomplish with this app?
The project’s goal was to create a tool for quick prototyping when building image-centric sites.
How did you use Redis to develop your app, and what other components were used along the way to create the final product?
I started development by getting images from Unsplash in all my categories and converting them into JSON as the metadata. RedisJSON and RediSearch were used to house this data; the images were stored on AWS S3.
The entire app was built using Next.js, the client that served as the demo and server for calling the endpoints. The endpoints were:
My name is Fred Spencer, and I am an Experience Architect in the United States. I’m the founder of Elm Story, a design tool and platform for interactive storytelling.
What technological components helped you realize this project?
The entire Meatballs.live project is written in TypeScript, utilizing Redis Stack features, including RedisGraph, RedisJSON, RedisTimeSeries, Pub/Sub, and caching. I used RedisInsight extensively to visually surface insights as data was collected in real-time. Redis Cloud hosts the primary Redis database.
Get more of the technical details on dev.to.
What professional pain points is Meatballs.live designed to solve?
You can think of this project as a “super-aggregator” designed to ingest, remix, and blend data from disparate aggregation sources.
By connecting and analyzing large amounts of structured, temporal data, meatballs.live can generate daily collections of top stories with a bias for the comment section. Daily collections serve as recommendations for the most engaging comments and related stories. The app experience can save time and cognitive load for users by reducing addictive scrolling. Temporal aspects provide context.
The live chat feature enables real-time engagement between meatballs.live users. The latest comments from Hacker News are blended with the stream, providing links to relevant threads.
Are you planning to do more with this project? If you had/have time to improve it, what would you add?
My number one priority is to warehouse historical data. With one data source, Meatballs.live generates 1 GB/mo. Given the current app’s feature set, it is unnecessary and inefficient for all this data to live in-memory. Next, I hope to add support for additional data sources, such as Reddit and Twitter.
I’d also like to port ingest services from Node to Rust, enhance live chat to support more real-time insight, and expand user features to include collection reactions.
There are no limits when remixing big data with the Redis Stack.
We want to thank everyone who participated in our Hackathon with dev.to. We saw some truly inspired ideas come to fruition and hope to see these Redis-built applications go to market soon!
To see more applications built with Redis, please visit our Launchpad site, full of engaging demos and inspiration for anyone building applications.