Ìlérí⚡️ @pipe_dev

Linesman @brimblehq brimble.io Poguelandia Joined July 2019

Tweets

21K
Followers

6K
Following

925
Likes

15K

8. @hen8y

7 hours ago

+234 tech space, na larpers full am.

5 11 49 1K 2

View Details

Ìlérí⚡️ @pipe_dev

2 hours ago

@lanreadelowo All roads leads to an IDE, it’s even linear I’m waiting for 😂

0 0 0 24 0

View Details

Ìlérí⚡️ @pipe_dev

2 hours ago

@lanreadelowo You are in for a ride, better language design than ts.

0 0 0 24 0

View Details

Bachs @bachs_hq

7 hours ago

@pipe_dev Looks like us

0 0 0 22 0

View Details

We’re excited to announce Rubbie Kelvin (@KelvinRubbie) as a speaker at SysConf 2026! His talk is titled “The Autopsy of an Asynchronous Deadlock.” Async Rust promises fearless concurrency, but the runtime can still lock up, and when it does, no stack trace exists to point you to the culprit. This talk walks through a deadlock Rubbie hit in a production Tokio-based service, using it as a case study for a general forensic method. How do we recognize a deadlock vs a slowdown? How do we use tokio-console to see relevant task state? How do we reason about lock ordering, .await points and task starvation? Come find out at this talk! #SysConf #SysConf26

3 9 30 2K 4

View Details

Ìlérí⚡️ @pipe_dev

21 hours ago

Brimble Credit Wallet is now live. You can fund your wallet in USD or supported local currencies, then use that balance to pay for your subscription, domains, build minutes, and other services on Brimble. We built this for teams and businesses that want to use Brimble but are blocked by dollar cards or card restrictions. No dollar card? You can still use Brimble.

6 23 123 2K 18

View Details

tø2by @Dev_Tobby

15 hours ago

I worked on an experiment using the same microservice architecture and the same load, but with two different retry strategies. The first setup used the normal approach most systems use: if a downstream request fails, retry it. The problem is that in a chain of microservices, that failure can keep moving upward. For example: Gateway → Checkout → Inventory → Stock If Stock fails, Inventory retries it. If Inventory still returns an error, Checkout may retry Inventory. Then Gateway may retry Checkout again. So one failure deep in the system can create retries at multiple layers, even though the original problem is still just Stock. That becomes much more dangerous in larger systems with 10+ services or during heavy traffic. A service is already struggling, then retries from several layers create even more traffic and make the failure worse. So I tested a different approach, retry ownership. The idea is simple, identify where the failure actually originated and allow the retry to happen only at the layer closest to that failure. If Stock is failing, Inventory owns that retry. If Inventory retries Stock and it still fails, the error is propagated upward, but Checkout and Gateway do not retry the same failure again. In my baseline test, retries happened across the whole chain: Gateway → Checkout: 316 retries Checkout → Inventory: 480 retries Inventory → Stock: 930 retries After adding retry ownership: Gateway → Checkout: 0 retries Checkout → Inventory: 0 retries Inventory → Stock: 1,563 retries The retry work moved to the place where it was actually useful instead of being duplicated across the system. This also makes failures easier to understand operationally. Instead of seeing retries everywhere and trying to figure out which service is actually unhealthy, the retry activity stays close to the real problem. That makes it easier to debug, easier to see where capacity is needed, and reduces the chance of one downstream failure creating unnecessary work across the rest of the system. Retry ownership is basically about making retries intentional.

tø2by @Dev_Tobby

15 hours ago

Rerty Ownership in Microservices

0 0 1 1K 0

2 3 29 2K 7

View Details

Ìlérí⚡️ @pipe_dev

20 hours ago

@aydahnizzy x.com/pipe_dev/statu…

Ìlérí⚡️ @pipe_dev

a day ago

@aydahnizzy i pity you.

0 0 0 457 0

0 0 0 345 0

View Details

Ìlérí⚡️ @pipe_dev

21 hours ago

Even performs better than NodeJs on that spec If you are building a binary, it’s way smaller too. You didn’t even say android studio 😔

Stanlee.dev @stanlee0nX

a day ago

You want to learn Golang with your 4GB Ram laptop, I Dey laugh you

66 12 180 32K 12

4 2 62 3K 3

View Details

Ìlérí⚡️ @pipe_dev

21 hours ago

Learn more about wallets here: paper.brimble.io/billing/wallet

0 0 4 159 1

View Details

Ìlérí⚡️ @pipe_dev

22 hours ago

Highly available postgres instance. A very interesting implementation I did with patroni and consul.

2 3 32 1K 11

View Details

Ìlérí⚡️ @pipe_dev

22 hours ago

Jokes on you.

Stanlee.dev @stanlee0nX

a day ago

You want to learn Golang with your 4GB Ram laptop, I Dey laugh you

66 12 180 32K 12

2 1 26 3K 0

View Details

Ìlérí⚡️ @pipe_dev

a day ago

@Dev_Tobby Yes, works extremely well with k8. I had issues with it with nomad, and I ended up doing a lot of iptable configuration

0 0 0 29 0

View Details

Ìlérí⚡️ @pipe_dev

a day ago

@aydahnizzy i pity you.

0 0 0 457 0

View Details

Ìlérí⚡️ @pipe_dev

a day ago

Oloshi 😂😂 Sportyclaw landing page is deployed on @brimblehq

P! @iPariola

a day ago

“Found my way” 🙂‍↔️

0 0 8 9K 1

3 1 52 8K 7

View Details

Ìlérí⚡️ @pipe_dev

a day ago

@grtsnx @brimblehq Active sir.

1 0 1 43 0

View Details

Ìlérí⚡️ @pipe_dev

3 days ago

S3 buckets are now available in Lagos 🇳🇬 You can now store your files closer to users in West Africa for lower latency and faster uploads/downloads. Available now on @brimblehq . paper.brimble.io/object-storage…