memoize
django-hurricane
memoize | django-hurricane | |
---|---|---|
1 | 5 | |
64 | 69 | |
- | - | |
6.2 | 5.7 | |
7 days ago | 15 days ago | |
Python | Python | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
memoize
-
Good and Bad Elixir
I totally agree, though I think those articles are a lot harder (eg requiring more skill) to write well because you need to quickly ramp your readers on all of whatever the context is that's necessary to actually appreciate the nuance of the design decisions under discussion. You're basically by definitely going to be out of the realm of "just follow best practice X" or "apply pattern Y or you're doing it wrong."
As a small example, I've been working on a small asyncio-based web service (Python) which is oriented around an expensive process that generates a result, where the result is stashed in sqlite and returned. I knew upfront that I needed a way to track when a particular result was already being prepared so that if I got a second request for it, it would collapse it into the first one and only do the work once. I wrote this as a twenty line memoizing decorator, but it turns out this issue as a nameβ cache stampeding. Once I realized that, I discovered that there are existing (and much more complicated/tunable) solutions to this problem, such as https://github.com/DreamLab/memoize/, but the article pitching that solution spends quite a bit of time getting to itβ enough so that if I'd discovered it before building my own, I'm not sure I would even have appreciated its applicability:
https://tech.ringieraxelspringer.com/blog/open-source/cachin...
django-hurricane
-
Microservices in Django
Btw: We're working on making Django as simple as possible to run on Kubernetes with the principles of the 12Factors and Kubernetes patterns, have a look: https://django-hurricane.io (and there are tutorials, too)
-
What are some must use libraries? Give the name and a quick description please!
Lots of cool stuff already. I'd like to add django-hurricane (https://django-hurricane.io/) for Kubernetes deployment scenarios.
-
OpenTelemetry and Python: A Complete Instrumentation Guide
Thank you very much! This will be (among others) a basis for my effort to integrate the OpenTelemetry instrumentation in Django Hurricane (https://django-hurricane.io).
-
Django K8s resource requests and limits
In order to grasp that problem a little bit, we've started Django Hurricane: https://django-hurricane.io/
-
Put Django to Kubernetes with Django-Hurricane
We recently started an new open source project: django-hurricane (https://github.com/Blueshoe/django-hurricane). The idea is to fit applications made with the django web framework perfectly into Kubernetes. A step towards Kubernetes-native development.
What are some alternatives?
httpx-cache - Simple caching transport for httpx
webssh - :seedling: Web based ssh client
Tornado-SQLAlchemy - SQLAlchemy support for Tornado
hera - Hera is an Argo Python SDK. Hera aims to make construction and submission of various Argo Project resources easy and accessible to everyone! Hera abstracts away low-level setup details while still maintaining a consistent vocabulary with Argo. βοΈ Remember to star!
Mockintosh-Samples
pottery - Redis for humans. πππ
turbo - A framework based on tornado for easier development, scaling up and maintenance
ReducePy - URL shortener service using Tornado and Redis runs on Docker and Kubernetes.
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
cacheme - Asyncio cache framework for Python