How To Include Redis In Your Application Architecture

Episode • Mar 4, 2019 • 1h 1m

Summary

The Redis database recently celebrated its 10th birthday. In that time it has earned a well-earned reputation for speed, reliability, and ease of use. Python developers are fortunate to have a well-built client in the form of redis-py to leverage it in their projects. In this episode Andy McCurdy and Dr. Christoph Zimmerman explain the ways that Redis can be used in your application architecture, how the Python client is built and maintained, and how to use it in your projects.

Announcements

Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
When you’re ready to launch your next app or want to try a project you hear about on the show, you’ll need somewhere to deploy it, so take a look at our friends over at Linode. With 200 Gbit/s private networking, scalable shared block storage, node balancers, and a 40 Gbit/s public network, all controlled by a brand new API you’ve got everything you need to scale up. Go to pythonpodcast.com/linode to get a $20 credit and launch a new server in under a minute. And don’t forget to thank them for their continued support of this show!
And to keep track of how your team is progressing on building new features and squashing bugs, you need a project management system designed by software engineers, for software engineers. Clubhouse lets you craft a workflow that fits your style, including per-team tasks, cross-project epics, a large suite of pre-built integrations, and a simple API for crafting your own. Podcast.__init__ listeners get 2 months free on any plan by going to pythonpodcast.com/clubhouse today and signing up for a trial.
Visit the site to subscribe to the show, sign up for the newsletter, and read the show notes. And if you have any questions, comments, or suggestions I would love to hear them. You can reach me on Twitter at @Podcast__init__ or email hosts@podcastinit.com)
To help other people find the show please leave a review on iTunes and tell your friends and co-workers
Join the community in the new Zulip chat workspace at pythonpodcast.com/chat
You listen to this show to learn and stay up to date with the ways that Python is being used, including the latest in machine learning and data analysis. For even more opportunities to meet, listen, and learn from your peers you don’t want to miss out on this year’s conference season. We have partnered with O’Reilly Media for the Strata conference in San Francisco on March 25th and the Artificial Intelligence conference in NYC on April 15th. Here in Boston, starting on May 17th, you still have time to grab a ticket to the Enterprise Data World, and from April 30th to May 3rd is the Open Data Science Conference. Go to pythonpodcast.com/conferences to learn more and take advantage of our partner discounts when you register.
Your host as usual is Tobias Macey and today I’m interviewing Andy McCurdy and Christoph Zimmerman about the Redis database, and some of the various ways that it is used by Python developers

Interview

Introductions
How did you get introduced to Python?
Can you start by explaining what Redis is and how you got involved in the project?
How does the redis-py project relate to the Redis database and what motivated you to create the Python client?
What are some of the main use cases that Redis enables?
Can you describe how Redis-py is implemented and some of the primitives that it provides for building applications on top of?
- How do the release cycles of redis-py and the Redis database relate to each other?
- How closely does redis-py match the features of the Redis database?
- What are some of the convenience methods or features that you have added to make the client more Pythonic?
Redis is often used as a key/value cache for web applications, in some cases replacing Memcached. What are the characteristics of Redis that lend themselves well to this purpose?
- What are some edge cases or gotchas that users should be aware of?
What are some of the common points of confusion or difficulties when storing and retrieving values in Redis?
What have been some of the most challenging aspects of building and maintaining the Redis Python client?
What are some of the anti-patterns that you have seen around how developers build on top of Redis?
What are some of the most interesting or unexpected ways that you have seen Redis used?
What are some of the least used or most misunderstood features of Redis that you think developers should know about?
What are some of the recent and near-future improvements or features in Redis that you are most excited by?

Keep In Touch

Andy
- @andymccurdy on Twitter
- andymccurdy on GitHub
Christoph
- chrisAtRedis on GitHub
- LinkedIn

Picks

Tobias
- Rowan Atkinson
Andy
- The Food Lab: Better Home Cooking Through Science by J. Kenji Lopez-Alt
- Dota 2 Auto Chess (Community Mod)
Christoph

Switch to the Fountain App

Open in Fountain