Dev_Ologun

Building apps end-to-end | Training models | Shipping on-chain | Web3 maximalist

[Dev_Ologun @Dev_Ologun]

@Obasi_C_J Activeee 💪💪💪

[Dev_Ologun @Dev_Ologun]

Valentine na for people wey their code dey run without error. We move. 🚶‍♂️💻

[Dev_Ologun @Dev_Ologun]

I'm actively following anyone who follows or comment
Let's grow together 💪💪💪

[Dev_Ologun @Dev_Ologun]

@Badboy1B Hello

[Dev_Ologun @Dev_Ologun]

@RiazBaby Yes
I Follow Back ASAp

[Dev_Ologun @Dev_Ologun]

@arifhossen1620 Yes. I follow back ASAP

[Dev_Ologun @Dev_Ologun]

What do we call someone who studies "Chaos Engineering"

An Engineer of Chaos😂😂😂

[Dev_Ologun @Dev_Ologun]

Make payments, emails, and state changes idempotent.

How: Use unique request IDs.
If the ID is already processed then return “success” without doing it again.

One rule that prevents millions in losses.

#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Day 19/100

Most outages happen because a retry action created duplicates (double charges, double emails).

The question is: “Is this operation safe to retry?”

#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Strong consistency required in money, seats, inventory, usernames
Eventually consistent is OK in likes, views, recommendations, news feed

Write this table on Day 1.
It decides your database, queues, and service boundaries for the next few years.

#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Day 18/100

Most “can’t scale” issues are actually hidden consistency bugs.

List every piece of data and answer:
→ Can it be eventually consistent?
→ Or must it be strongly consistent?

#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Write the runbook before you write the code.

“One-click rollback” and “how to restore money” are the only features that would matter when shit hits the fan.
#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Day 17/100

If your system has no documented “runbook” for the worst failure then it will fail exactly that way at 3 am on a random unexpected day.

#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Good errors tell exactly:
- What failed
- Why it matters
- What the user can do next

Vague errors = lost money + lost trust.

Make errors part of the design, not an afterthought.
#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Day 16/100

If your error message says “Something went wrong”
then your entire architecture just lied to the user and the team.

#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Real architecture skill isn’t adding new services.

It’s having the courage to kill the old ones that everyone is afraid to touch.

In order words break that codebase even if it still manages to work

Delete first then Design a second one.
#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Day 15/100

The dirty secret nobody says out loud:

Most “system redesigns” happen because someone was too scared to delete old code.

#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

If a change takes more than 15 minutes from commit to live then your architecture is broken, no matter how many microservices you have.

Deploy speed is the ultimate test of any architecture.
#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Day 14/100

Perfect architecture on paper is useless
if the team can’t deploy features 10 times per day without breaking production.
#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Database choice, data model, consistency rules, transaction boundaries = your entire architecture.

Decide these on Day 1 based on your deadly decisions (Day 11), not on what’s trendy.
#100DaysOfArchitecture

[Dev_Ologun @Dev_Ologun]

Day 13/100

“We’ll choose the database later”
is the fastest way to waste 6–12 months of engineering time.

#100DaysOfArchitecture