Event Sourcing is like Time traveling.

I know we can travel back (we technically called it "reproducibility"), but can we travel to the future?

Data is the most critical part of your infrastructure.

Lose your network? That's just downtime.

Lose your data? That's game over.

Have you ever lost production data?

A survival kit to beat APIs interview.

Here are 11 questions you need to know how to answer.

A good API is like great architecture—invisible when done well, painful when done poorly.

It feels natural and intuitive. It simply works!

My goal for next year: help more software engineers pass the System Design interview.

My favorite way to handle distributed transactions is using SAGAs.

It does not provide true atomicity but helps with:

- Eventual Consistency
- Compensating Transactions
- Scalability
- Fault Tolerance

Nobody told me I would miss my JOINs when I started in microservices.

Relational Databases are so good at joining data that we often forget until we miss our JOINs.

Breaking the database apart is one of the most complex tasks.

No matter what the books say, nobody likes making 20 requests to render a page.

3 proven Aggregation Patterns your consumers will love.👇

Exceptional Resumes tell a story:

- Your skills
- Your Impact
- How you're the right fit

I can't think of a better Non-Technical skill than learning to negotiate.

If you are a:

- Freelancer? You’re negotiating your estimates, scope, and payment terms all day.

- Employee? You’ve got salary, promotions, and perks on the table.

Best book I have ever read on negotiation. 👇

Build Resilient Interactions, Not Just Resilient Services!

5 things a truly resilient system needs.

1. Caching
2. Prevent Cascading Failures
3. Fallback Behaviors
4. Retry Wisely
5. Go Asynchronous

Read the full article here. 👇

newsletter.systemdesignclassroom.com/p/focus-on-b...

System design is just a collection of messy trade-offs.

• Sql vs NoSql
• Consistency vs Availability
• Accuracy vs Latency
• Strong vs Eventual Consistency
• Batch vs Stream Processing
• Synchronous vs Asynchronous Processing
• Duplication vs Normalization
• TCP vs UDP

There are many anti-patterns in microservices.

But Content Coupling is the worst.

When one service directly accesses another's database, you risk:

- Unclear ownership
- Duplicated logic
- Data corruption

Don’t share schemas -> share APIs! 👇

newsletter.systemdesignclassroom.com/p/dont-share...

💚 Tomorrow will be a special occasion

@gabortill.bsky.social Engineering Manager turned Mentor & Coach for Software Engineers will share a 7-step guide to help you reach your goal from Software Engineer to leadership.

Get it in your inbox 👇🏼

newsletter.optimistengineer.com

#SoftwareEngineer

80% of System Design Interviews are based on 20% of the problems.

Here is what you need to master. 👇

1. Scalable Data Storage
2. Caching
3. Load Balancing
.
.
.

www.linkedin.com/posts/raul-j...

If you master these 11 areas, you'll be ready for most system design interviews thrown at you.

Idempotency is underrated and under-implemented. 

Too many systems cannot handle retries, turning simple issues into complex failures.

Here is a simple way to implement it.

@rauljuncov.bsky.social Happy to see you in this space!

If folks around doesn't know Raul's work, here it is! 👇🏽

newsletter.systemdesignclassroom.com?r=nw9bj

#systemdesign

System Design isn't Kubernetes.

System Design is making tough trade-offs under pressure and understanding why one approach is better than another.