RaulJuncoV's profile picture. I simplify System Design, and System Design will make you a better Software Engineer. 

System Design • Databases • Algorithms • AI Enthusiast

Raul Junco

@RaulJuncoV

I simplify System Design, and System Design will make you a better Software Engineer. System Design • Databases • Algorithms • AI Enthusiast

置頂

I have been in backend development for more than 15 years. It is a challenging field and It took me some time to find my path to becoming a good one. But if I started over, these are the 6 steps I would follow. 1 of 6


Most teams think schema validation is enough for their data pipelines. That’s why their streaming data quality is broken. Schemas catch structure. Semantic validation catches meaning. - email must look like an email - person's age can’t be -3 or 999 - amount must be positive…

RaulJuncoV's tweet image. Most teams think schema validation is enough for their data pipelines.

That’s why their streaming data quality is broken.

Schemas catch structure.
Semantic validation catches meaning.

- email must look like an email
- person's age can’t be -3 or 999
- amount must be positive…

We’re finally moving past vibe coding. Prompt, Pray, and Compile is not engineering. And now, we’re seeing a new generation of AI tools that are doing exactly what we’ve been waiting for. They don’t just autocomplete. They think. They plan. They deliver. The one that caught…


Raul Junco 已轉發

Most outages don’t come from bad code. They’re caused by assumptions no one bothered to question. Systems don’t break because people are careless. They break because something “obvious” never got said out loud. The killers are always the silent parts: - “This API will never…

RaulJuncoV's tweet image. Most outages don’t come from bad code.
They’re caused by assumptions no one bothered to question.

Systems don’t break because people are careless.
They break because something “obvious” never got said out loud.

The killers are always the silent parts:

- “This API will never…

Raul Junco 已轉發

On paper, CDC decouples producers from event publishing. In practice, it couples consumers to the producer’s database design. Most teams adopt Change Data Capture to “go event-driven” without touching their code. Flip a switch. Stream your DB changes. Done. Until the cracks…

RaulJuncoV's tweet image. On paper, CDC decouples producers from event publishing.

In practice, it couples consumers to the producer’s database design.

Most teams adopt Change Data Capture to “go event-driven” without touching their code.
Flip a switch. Stream your DB changes. Done.

Until the cracks…

Raul Junco 已轉發

Your cache isn’t broken because of LRU. It’s broken because you forgot TTL. Why LRU Alone Fails 1. Stale data: Hot keys never expire. Yesterday’s price lives forever. 2. Idle memory: If the cache never fills, nothing gets evicted. Dead keys stay. 3. Broken correctness: Wrong…

RaulJuncoV's tweet image. Your cache isn’t broken because of LRU.

It’s broken because you forgot TTL.

Why LRU Alone Fails

1. Stale data: Hot keys never expire. Yesterday’s price lives forever.
2. Idle memory: If the cache never fills, nothing gets evicted. Dead keys stay.
3. Broken correctness: Wrong…

Raul Junco 已轉發

A common mistake I see: People treat message queues and streams as if they’re interchangeable. They’re not. Here’s the difference 👇 Message Queue (MQ) - Designed for delivery guarantees (at-least-once, exactly-once). - Great for sporadic workloads and asynchronous tasks. -…

RaulJuncoV's tweet image. A common mistake I see:

People treat message queues and streams as if they’re interchangeable.

They’re not.

Here’s the difference 👇

Message Queue (MQ)

- Designed for delivery guarantees (at-least-once, exactly-once).
- Great for sporadic workloads and asynchronous tasks.
-…

Raul Junco 已轉發

If you can’t explain these formulas, you’re not ready to talk about availability. Most engineers screw this up. They think: “If my components are reliable, my system is reliable.” Wrong. Here’s the trap: - Two components with 99.9% availability - Put them in sequence → total…

RaulJuncoV's tweet image. If you can’t explain these formulas, you’re not ready to talk about availability.

Most engineers screw this up.

They think: “If my components are reliable, my system is reliable.”
Wrong.

Here’s the trap:

- Two components with 99.9% availability
- Put them in sequence → total…

Loading...

Something went wrong.


Something went wrong.