🔐 Ash Finds a Locked Chest, Redis Guards the Door, and RSA Asks for the Secret Key

The ones where Ash doesn't win a Gym Badge.

Nobody catches a legendary Pokémon.

There isn't even a massive battle.

Instead, Ash spends the entire day trying to understand something that looks completely confusing at first.

Today felt like one of those episodes.

Except my mysterious Pokémon wasn't Pikachu.

It was RSA.

😂🔐

The day started with cryptography.

More specifically…

The mathematics behind RSA.

I had already heard about public keys and private keys.

But today I went deeper.

How are the keys actually connected?

Why does the mathematics work?

How does someone encrypt something with one key and somehow allow only the other key to unlock it?

The more I studied it, the more it felt like Ash discovering that the strange locked chest wasn't actually locked by magic.

There was mathematics behind it.

Then came the Euclidean Algorithm.

And honestly…

This was one of those topics that looks simple until your college professor puts a numerical in front of you.

😂

The idea itself is beautifully simple.

Keep reducing the problem.

Use the remainder.

Repeat.

Eventually…

You reach the answer.

But then came the Extended Euclidean Algorithm.

And suddenly the simple journey became a little more interesting.

Now I wasn't just finding the greatest common divisor.

I was also finding the coefficients that help make the mathematics behind cryptography work.

That was the moment I started seeing the connection.

The algorithms weren't just college numericals anymore.

They were part of the machinery behind real security systems.

🧠

I spent some time solving numericals at college too.

And honestly, this was probably one of those moments where I thought,

"Why am I doing this again?"

But then I remembered something.

The things that feel boring today often become the things that make complicated concepts easier tomorrow.

You don't always appreciate the foundation while you're standing on it.

Later, I returned to SentiOps.

And this time…

Redis was waiting.

🟥

I had already used Redis before.

But today I started looking at it from a more production oriented perspective.

What actually happens when an application connects to Redis?

Does every request create a brand new connection?

What happens when hundreds of requests arrive?

And then I discovered the idea of a Redis Connection Pool.

Suddenly the picture became much clearer.

Instead of constantly creating and destroying connections, the application can reuse existing connections.

It's like Ash having a Pokémon team ready before every battle.

Why call Professor Oak every single time you need Pikachu?

Just keep the team ready.

😂⚡

That simple idea made me think about production differently.

Creating connections isn't free.

It takes resources.

Time.

Overhead.

So if an application constantly creates new Redis connections, it can become inefficient.

A connection pool helps manage those connections more intelligently.

Simple concept.

Very important in real systems.

Then came Redis TTL.

This one felt almost like a timer attached to every piece of information.

You put something into the cache.

And you tell Redis,

"You can keep this for a while."

Then…

Time passes.

⏳

The data disappears.

Automatically.

No one has to manually clean everything.

That is where TTL becomes incredibly useful.

Especially when cached data shouldn't live forever.

But then came the bigger question.

What happens when the original data changes?

Now the cache might be holding an old version.

And suddenly…

We have stale data.

That's where Cache Invalidation enters the story.

And honestly, this might be one of those problems that sounds easy until you're actually dealing with a production system.

Because keeping data in a cache is easy.

Keeping the cache correct…

That's the real challenge.

This is where today's learning started connecting together.

Redis isn't simply,

"Store something and retrieve it quickly."

Production caching requires thinking about lifecycle.

When should data enter?

When should it expire?

When should it be removed?

What happens when the original data changes?

What happens when Redis goes down?

Those questions are what turn a simple cache into an engineering problem.

🧠

Was today highly productive?

Honestly…

Maybe not.

I didn't finish some massive project.

I didn't deploy something groundbreaking.

There wasn't a huge milestone to celebrate.

But when I look back at the day…

I learned RSA mathematics.

Revised Euclidean algorithms.

Solved numericals.

Deepened my understanding of Redis.

Learned connection pools.

Understood TTL.

Explored cache invalidation.

And connected all of it back to SentiOps.

Maybe that's not a bad day after all.

🌱

Ash sometimes had days where he didn't win anything.

But those days still mattered.

Because every journey isn't measured by how many badges you collect.

Sometimes you measure it by how many things finally make sense that didn't make sense yesterday.

Today…

A few more things clicked.

And that's enough.

🧠 Tiny Crux Before Closing My Laptop

🔐 RSA became more interesting once I started understanding the mathematics behind how its keys actually work.

🧮 Euclidean and Extended Euclidean Algorithms showed me that algorithms I solve as college numericals also have real importance in cryptography.

🟥 Redis Connection Pools taught me why production applications shouldn't constantly create and destroy connections when they can efficiently reuse them.

⏳ Redis TTL showed me how cached data can automatically expire instead of living forever.

🧹 Cache Invalidation reminded me of one of the oldest problems in software engineering. Keeping cached data fast is easy. Keeping it correct is much harder.

🤖 SentiOps continues to give me a reason to learn these concepts beyond theory. Every new technology becomes more meaningful when I can imagine where it belongs inside a real production architecture.

🌱 The biggest lesson today was that not every productive day feels productive.

Some days you build.

Some days you revise.

Some days you solve college numericals.

And some days you simply unlock one more door.

Today…

I think I unlocked a few.

Now let's see what's waiting behind them tomorrow. ⚡🔐