Erick Emmanuel

[Pirat_Nation 🔴 @Pirat_Nation]

A Minecraft modder is developing a modpack focused on mech action inspired by Armored Core, set in a post-apocalyptic world where players can explore, obtain, and upgrade their own mech.

[Historic Vids @historyinmemes]

I still have no idea how people traveled these seas 500 years ago

[Ashish Pratap Singh @ashishps_1]

Top 5 Caching Strategies Explained:

1. 𝐑𝐞𝐚𝐝 𝐓𝐡𝐫𝐨𝐮𝐠𝐡: The application always queries the cache first. If the data is not in the cache (cache miss), the cache itself fetches it from the database and stores it for future requests.

Pros: Simplifies application logic, ensures cache always has fresh data.
Cons: Higher cache complexity, might not suit write-heavy systems.

👉 Best for: Read-heavy apps like CDNs, social media feeds, and user profiles.

2. 𝐂𝐚𝐜𝐡𝐞 𝐀𝐬𝐢𝐝𝐞 (𝐋𝐚𝐳𝐲 𝐋𝐨𝐚𝐝𝐢𝐧𝐠): The application first checks the cache. If the data isn't found (cache miss), it fetches it from the database and stores it in the cache for subsequent requests.

Pros: Keeps cache small, avoids unnecessary data in memory.
Cons: Cache misses can be expensive, risk of stale data if updates are frequent.

👉 Best for: Systems with a high read-to-write ratio, like e-commerce sites.

3. 𝐖𝐫𝐢𝐭𝐞 𝐓𝐡𝐫𝐨𝐮𝐠𝐡: Every write operation is first stored in the cache, then immediately written to the database.

Pros: Ensures cache and database are always in sync.
Cons: Higher write latency, unnecessary caching of rarely accessed data.

👉 Best for: Consistency-critical systems, such as financial apps.

4. 𝐖𝐫𝐢𝐭𝐞 𝐀𝐫𝐨𝐮𝐧𝐝: The application directly writes to the database, bypassing the cache. The cache gets updated only when a read request occurs.

Pros: Avoids caching rarely accessed data.
Cons: Higher cache miss rate, causing frequent database reads.

👉 Best for: Write-heavy systems where data isn’t immediately needed, like logging systems.

5. 𝐖𝐫𝐢𝐭𝐞 𝐁𝐚𝐜𝐤: Data is first written to the cache, and the cache asynchronously updates the database in the background.

Pros: Super-fast writes, reduces database load.
Cons: Risk of data loss if the cache crashes before syncing with the database.

👉 Best for: High-write throughput systems, such as social media feeds.

𝐖𝐡𝐢𝐜𝐡 𝐂𝐚𝐜𝐡𝐢𝐧𝐠 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐲 𝐒𝐡𝐨𝐮𝐥𝐝 𝐘𝐨𝐮 𝐔𝐬𝐞?

- If reads are more frequent → Read-Through / Cache-Aside
- If writes need to be consistent → Write-Through
- If you want to minimize unnecessary caching → Write-Around
- If you need ultra-fast writes → Write-Back

♻️ Repost to help others in your network.

[Nathie @nathie]

Microsoft Flight Simulator in VR is an absolutely breathtaking experience!

[🌙 mini textos @itextosoff]

Tu paz vale más que cualquier cosa

[🌙 mini textos @itextosoff]

Sé tu prioridad

[Dan @danielgoaz]

Es la peor forma de perderla.

[Buitengebieden @buitengebieden]

This.. 🥺

[Ⓜ️🇲🇽🅰️ 𝓢𝓸𝓵𝓲𝓼 @chivassolis]

Ojala coincidas con alguien que en verdad sepa lo que vales.🧠🫀✨❤️‍🩹

[Jairo Guerrero @JaiiWriter]

Libro: “12 Maneras de Amar(te)” 📙

[Cementerio De Libros @Cementedelibros]

Por si quieres, ven y acuéstate a mi lado…
José Vergara
#cementeriodelibros

[illcamp COMMS OPEN| NOT AI 🚫 @illcamp666]

Heyy do you remember when you loved my ZeldaxGhibli redraws last year? Well I'm currently unemployed and this close 🤏 to become homeless so if you want a cute print of my art you can buy it here and it would help me a lot! Thank youuuu https://t.co/6aTJqM8Gtx

[Jairo Guerrero @JaiiWriter]

6 de junio. ✍🏼