Started new post
This commit is contained in:
parent
f2c200bd7b
commit
a6ad7e20b7
20
content/post/python-and-redis.md
Normal file
20
content/post/python-and-redis.md
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
---
|
||||||
|
title: "Python and Redis"
|
||||||
|
date: 2018-01-02T21:16:01-05:00
|
||||||
|
draft: true
|
||||||
|
tags: ["python", "redis"]
|
||||||
|
---
|
||||||
|
|
||||||
|
# Python, Redis, and You
|
||||||
|
|
||||||
|
As a developer I've used a lot of NoSQL stores for a lot of things. Usually as
|
||||||
|
messaging substrates, but also to hold volatile data as well. My favorite is to
|
||||||
|
employ these services as a message queue between different applications. In past
|
||||||
|
projects that I have been a part of, we have had several microservices running
|
||||||
|
at the same time in AWS that needed a scalable means to talk to eachother. With
|
||||||
|
some REST. Ha, so most times what we reached for a key-value store known as
|
||||||
|
Redis.
|
||||||
|
|
||||||
|
## Some key points
|
||||||
|
|
||||||
|
What Redis has offered us was a scalable nosql db
|
Loading…
Reference in New Issue
Block a user