🧩 По полочкам. Кэширование.
• Логически кэш представляет из себя базу типа ключ-значение. Каждая запись в кэше имеет “время жизни”, по истечении которого она удаляется. Это время называют термином Time To Live или TTL. Размер кэша гораздо меньше, чем у основного хранилища, но этот недостаток компенсируется высокой скоростью доступа к данным. Это достигается за счет размещения кэша в быстродействующей памяти RAM. Поэтому обычно кэш содержит самые “горячие” данные.
• Если тема для вас показалось интересной, то вот очень объемная статья о том, как работает кэширование. Всё по полочкам, с картинками и примерами.
➡️https://pikuma.com/blog/understanding-computer-cache
#cache
https://realpython.com/blog/python/caching-in-django-with-redis/
Caching in #Django With #Redis
Application performance is vital to the success of your product. In an environment where users expect website response times of less than a second, the consequences of a slow application can be measured in dollars and cents. Even if you are not selling anything, fast page loads improve the experience of visiting your site.
Everything that happens on the server between the moment it receives a request to the moment it returns a response increases the amount of time it takes to load a page. As a general rule of thumb, the more processing you can eliminate on the server, the faster your application will perform. Caching data after it has been processed and then serving it from the #cache the next time it is requested is one way to relieve stress on the server. In this tutorial, we will explore some of the factors that bog down your application, and we will demonstrate how to implement caching with Redis to counteract their effects.
https://pypi.python.org/pypi/python-memcached
This software is a 100% Python interface to the #memcached#memory#cache daemon. It is the #client side software which allows storing values in one or more, possibly remote, memcached servers. Search google for memcached for more information.
#cplusplus#cache#cpp#database#fibers#in_memory#in_memory_database#key_value#keydb#memcached#message_broker#multi_threading#nosql#redis#valkey#vector_search
Dragonfly is a modern in-memory data store compatible with Redis and Memcached, offering up to 25 times higher throughput and better cache efficiency while using up to 80% fewer resources. It scales well with larger servers, supports many Redis commands, and features a unique, memory-efficient cache and fast snapshotting. Dragonfly provides low latency, high performance, and is easy to configure with familiar Redis options. Its design ensures atomic operations and efficient resource use, making it ideal for fast, cost-effective cloud applications needing real-time data access and high scalability. This means you get faster, more efficient caching and data handling with minimal changes to your existing setup[5][2][4].
https://github.com/dragonflydb/dragonfly
#java#cache#caffine#data#draft#fetch#graphql#immer#immutable#immutable_collections#immutable_datastructures#java#jdbc#kotlin#orm#orm_framework#orm_library#orms#redis#redis_cache
Jimmer is a powerful and advanced ORM (Object-Relational Mapping) framework for Java and Kotlin that lets you easily read and write complex data structures without needing to predefine their shapes. It supports dynamic multi-table queries, automatic SQL optimization, and efficient saving of incomplete or nested objects. Jimmer also generates type-safe DTOs (Data Transfer Objects) for complex queries and updates, avoids common problems like "N+1" queries, and offers strong caching and GraphQL support. This means you can build complex business logic faster and with less hassle, improving both development speed and code quality. It works well with modern IDEs and supports both Java and Kotlin seamlessly.
https://github.com/babyfish-ct/jimmer