DEVBLUEPRINTS

Blog

  • About the blog
  • Archive
  • Newsletter
  • RSS

Legal

  • Terms & Privacy
  • Contact
  • About me

Subscribe to the Newsletter

I authorize communications by email or other means and agree to the Terms and Privacy Policy

 

Blog
  • About the blog
  • Archive
  • Newsletter
  • RSS
Legal
  • Terms & Privacy
  • Contact
  • About me
© 2026 All rights reserved — Designed and built withFooter Heartpor Ednaldo Luiz
How to estimate storage growth with writes, replication, and retention
System Design•19 min read

How to estimate storage growth with writes, replication, and retention

A practical guide to calculating storage from writes per second, average data size, replication factor, and retention time before volume becomes cost or bottlenecks in production.

Foto de Ednaldo Luiz
Ednaldo Luiz•June 26, 2026

Latest posts

Freshly published articles, updated whenever new content drops.

Solutions Architecture: what it is, where it acts, and why it creates confusion
architecture
solutions architecture
+2

Solutions Architecture: what it is, where it acts, and why it creates confusion

Understand what Solutions Architecture really is, where this role fits among other architecture disciplines, and why its scope is still so often misunderstood in practice.

System Design
2340
Enterprise Software: what changes when the product needs to operate as a platform
software
architecture
enterprise
platform

Enterprise Software: what changes when the product needs to operate as a platform

Scale, availability, compliance, and integration stop being “extras” and become survival requirements. A practical guide to the trade-offs and decisions that separate a common system from an enterprise platform.

System Design
5690
Not every bug is an incident — and not every incident is a bug
software
incident management
bugs
sre
+1

Not every bug is an incident — and not every incident is a bug

Bugs and incidents are not synonyms. Understand the difference between technical defect and operational impact, and see why the same problem can end up in the backlog or require an urgent production response.

Cloud & DevOps
5550
Law of Demeter: reduce coupling and stop chaining
software design
java
object calisthenics
+4

Law of Demeter: reduce coupling and stop chaining

Enough “train wrecks”: apply the Law of Demeter to cut coupling, simplify tests, and protect your domain. See when to use it (and when to ignore it).

Back-end
118100

Newsletter

Get practical architecture & system design content

Short weekly briefs with real decisions and trade-offs: Java/backend, cloud, and data-driven intelligent systems. No spam.

I authorize communications by email or other means and agree to the Terms and Privacy Policy

 

Recommended posts

Posts selected for you to explore further.

12
Law of Demeter: reduce coupling and stop chaining

Law of Demeter: reduce coupling and stop chaining

Enough “train wrecks”: apply the Law of Demeter to cut coupling, simplify tests, and protect your domain. See when to use it (and when to ignore it).

February 06, 202612 min