memoize
cleanapi
memoize | cleanapi | |
---|---|---|
1 | 1 | |
64 | 31 | |
- | - | |
6.2 | 0.0 | |
7 days ago | over 2 years ago | |
Python | Python | |
Apache License 2.0 | GNU General Public License v3.0 only |
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...
cleanapi
-
CleanAPI library: creating Python microservice for 30 seconds
You are welcome to use CleanAPI. It would be great if you come up with fresh ideas. Please do not hesitate to make pull-request on https://github.com/vlakir/cleanapi
What are some alternatives?
httpx-cache - Simple caching transport for httpx
pycoingecko - Python wrapper for the CoinGecko API
Tornado-SQLAlchemy - SQLAlchemy support for Tornado
VAmPI - Vulnerable REST API with OWASP top 10 vulnerabilities for security testing
webssh - :seedling: Web based ssh client
cleanbay - The metasearch engine for torrents. Ads-free. Hassle free.
pottery - Redis for humans. πππ
Sakurajima - AniWatch.me Python API wrapper
turbo - A framework based on tornado for easier development, scaling up and maintenance
tracardi-api - This is TRACARDI API - It uses Tracardi backend.
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
falcon - The no-magic web data plane API and microservices framework for Python developers, with a focus on reliability, correctness, and performance at scale.