Update app for Python 3.12.3 and redis 6.1.0 #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kyle and Loris, your book on Redis Microservices was really important to me. There was so much in the book and the code example for me to learn. Updating the code to recent versions of Python3 and Redis was a great way to hammer in the concepts of microservices as well as asyncio and redis. I was especially intrigued by the idea of having multiple loosely coupled microservices driven from the same event stream, each one storing only what it needs in its own private database.
I have seen a number of difficult microservices architectures, with AWS EventBridge/Lambdas among the hardest to manage. I'm looking forward to hanging my new project off of Redis streams. I think that will be more resilient and maintainable than what I have seen before, with simple independent scaling for each microservice as you suggested in the book.
Anyway here is my contribution to the project. Thanks for considering it.