I wanted to see what considerations or opinions people had on memcached , how you are using it, and what you have built with it.
I think memcached is a pretty mature, good, distributed and volatile in-memory kv-store with a security track record (so it’s important to protect it when using).
Otherwise than that for every performance critical application i was able to fix the issues without adding memcached or similar to the stack.
I started contributing to Django and it was my first time with it, I’d never used it previously. I thought it was a neat application. Thanks for sharing your context about it.
Absolutely and you’re welcome - i do a bit in architectural context and from time to time i reevaluate most common technologies and products in that regard.
My impression is that docker made throwing systems together “too” easy (which is in principle a good thing). And i am often tempted (and probably others have the same issue) to begin thinking i “could” use this and that in the project to do something efficiently.
But in my experience, while you add some maintenance burden introducing new services (especially services even though this also applies to libraries in a reduced form) one does not necessarily have a solid indication to actually rely on.
I switched to a more agile tactics now: i carve out MVP per MVP indicating architectural issues, allowing for a better understanding of the problem space and reliable indications (requirements) which then may be addressed by refactorings (and these often turn out to be the first choice) or the introduction of new dependencies/services.
However - this shouldn’t become a mansplaining thread - i offer to share experience and discuss stuff. I never stop to learn. 