Article of the day

Microservices don't mean you need ten different servers from day one. Most teams start by splitting a large backend into smaller services while still running everything on a single VPS with Docker Compose. Each service has its own Docker image and container, and services communicate over HTTP, gRPC, or a message broker like RabbitMQ or Kafka. This already gives you independent deployments, better code organization, and the ability to update one service without rebuilding the entire backend.

As traffic grows, you start moving services onto their own VPSs based on their resource needs. An AI service might need a machine with more CPU and memory, while an authentication service can stay on a much smaller server. Shared infrastructure such as PostgreSQL, Redis, and RabbitMQ is also commonly moved to dedicated machines so they aren't competing with application services for resources. This approach lets you scale only the parts of the system that need it instead of scaling everything together.

A good migration to microservices is usually gradual. Start by identifying clear business domains like authentication, users, payments, notifications, or courses, then extract them one at a time into separate services. Once a service is independent, it should eventually own its own database instead of sharing one with every other service. That prevents services from directly changing each other's data, reduces tight coupling, and allows each database to be optimized, scaled, and maintained independently. The goal isn't to split everything as quickly as possible, but to create boundaries that make the system easier to develop, deploy, and scale over time.

Read the full article 👉 [ LINK ]

@devwitheyob
#TechVibe #Microservices #Docker #SystemDesign #ArticleOfTheDay

When I finished high school, my father took me on a trip into the countryside, and we visited over 8 different places. I learned a lot about how people live, what excites them, our culture, and many memories.

We also saw different natural places. I promised to make this kind of long trip at least every 3 years, but currently, moving freely is not something you can do, especially in the current situation.

I really wish things settle down and I will make the same kind of trip right after I graduate.

@Ihaveadream19
#trip

Article of the day

The tool list alone was 1.2 million tokens, 6x past the model's 200K-token context window, before it read a single prompt. A microservice exposes 2400 REST endpoints. The naive MCP spec approach generates one tool per endpoint, and that tool-list payload is what burns. We shipped this exact integration on a production agent platform and rolled it back within hours.

Read the full article 👉 [ LINK ]

@devwitheyob
#ArticleOfTheDay #MCP #SystemDesign

Looks like someone's about to land a new job 😋

#random #job

Article of the day

The planner estimated 200 rows. The actual count was 4.2 million. A dashboard query that loaded in 800 ms at launch now takes 12 seconds on 8 million rows. EXPLAIN ANALYZE shows a Nested Loop over a Seq Scan; a missing composite index on (tenant_id, created_at) turned a 2 ms Index Scan into a full table scan. We debugged this exact regression on multiple production teams.

Read full article 👉 [ LINK ]

@devwitheyob
#ArticleOfTheDay #backend #PostgreSQL

This is incredibly huge for us in Africa. DeepSeek V4 flash just launched a flash model that can compete with a top-tier ChatGPT model. Mind you, this is just a flash model, which means the Pro version is coming soon. The price difference is also huge. How are they making this efficient? https://api-docs.deepseek.com/quick_start/agent_integrations/codex

There are some kind of comforts that you don't wanna escape from

@devwitheyob
#TechVibe #random

banger!!

Article of the day

A customer gets charged for an order that never made it into the database. An order service publishes a Kafka event, then updates PostgreSQL. The database write fails after the event is already out, and a phantom order cascades downstream, inventory decremented, fulfilment notified, payment charged, all for an order that does not exist. Root-cause tracing is brutal: the event trail looks correct; the database is the one that disagrees. We debugged variants of this on multiple production Kafka-backed services.

Read full article 👉 [ LINK ]

@devwitheyob
#TechVibe #ArticleOfTheDay #SystemDesign #MicroService

Need a toxic motivation to make my bed, anything on your side😁

Be my guest in the comments😭

@devwitheyob
#random

Motivation of the day😁

I'll tell you how risky life is
You're not gonna get alive

@devwitheyob
#TechVibe #random

Let me tell you how this happened.

This opportunity actually came from Upwork. The CEO found my profile, reached out, and we had a quick chat about my backend and automation experience. After that, we scheduled a technical interview, and then they gave me a take-home project.

I probably overdid it a bit. 😅 I didn't just build the features they asked for, I added tests, cleaned everything up, and even deployed it to production with additional features and even bought Gemini API to test it. After that, they had me walk through the code with their senior developers and answer a bunch of technical questions. The final round was a behavioral interview.

A few days later, they sent me an offer.

The company is US-based with a branch here in Addis. I'll be working as a Full-Stack & Automation Engineer. The schedule is from 5 PM to midnight, which actually works well with my university classes, and it's a hybrid setup. They also offered accommodation in the office so that I can work from there for the summer, so I'll be moving to Addis.

I was just getting started to enjoy my break with fam and friends but I gotta go back and hustle😭

@devwitheyob
#TechVibe #JobUpdate

There are actually different ways it can do that.

L4 load balancers work at the transport layer. They don't care about URLs, headers, or request bodies. They simply look at things like the source IP, destination IP, TCP/UDP ports, and protocol, then forward the entire connection to a backend server. Since they don't inspect or process the HTTP request itself, they're extremely fast and can handle millions of connections with very little overhead.

L7 load balancers work at the application layer. They terminate HTTPS, inspect the HTTP request, and make routing decisions based on things like the URL, headers, cookies, or even the request method. This is what allows requests like /api, /admin, and /images to be sent to completely different services even though they're on the same domain.

That's why many production systems use both. An L4 load balancer sits at the edge and quickly distributes incoming connections, while L7 proxies behind it handle the smarter routing to the right application or microservice. It gives you the performance of L4 with the flexibility of L7.

@devwitheyob
#TechVibe #LoadBalancing #SystemDesignsig

Article of the day

One of the biggest reasons companies use gRPC is because it runs on HTTP/2. Unlike traditional HTTP/1.1, HTTP/2 allows multiple requests to travel over a single connection at the same time, reducing latency and connection overhead. It also supports streaming out of the box, so a server can continuously send updates to a client without opening new connections. That's why you'll often find gRPC powering communication between internal services like authentication, payments, AI inference, notifications, analytics, and other microservices. In many production systems, users interact with a REST API, but behind the scenes the services are talking to each other using gRPC for speed, reliability, and strong contracts.

Read full article 👉 [ LINK ]

@devwitheyob
#TechVibe #ArticleOfTheDay #SystemDesign

Think about one problem almost every family in Ethiopia has at some point: finding a home servant.

What's interesting is that even with unemployment going up, people are still struggling to find reliable workers. I don't think it's because people don't want to do the job. The real issue is that there's no proper system that understands both sides.

The worker wants a safe environment, respect, clear job responsibilities, fair treatment, and someone they can talk to if problems come up. The homeowner wants someone they can trust, someone reliable, and someone who actually does what was agreed. Right now, both sides go into it with uncertainty, and that's where most of the problems start.

The funny thing is, money isn't even the biggest issue. I know people who are willing to pay well above the normal rate, but they still can't find the right person. On the other side, there are people looking for work but afraid of ending up in a bad situation.

I genuinely think if someone create a serious business, that solves the trust problem instead of just matching workers with homeowners, it could become one of the biggest businesses in the country.

Just thinking out loud. what do you think guys

@devwitheyob
#TechVibe #BusinessIdea #ideas

The diagram is the load-balancing lesson in one picture, gRPC's HTTP/2 multiplexing is a feature in the protocol layer and a bug at the L4 routing layer. Every gRPC-in-K8s production incident eventually traces back to which line of this diagram is wrong.

@devwitheyob
#TechVibe #gRPC #API #SystemDesign

መልካም ሰንበት fam😊

@devwitheyob
#TechVibe #Sabbath

አንዳንድ ጊዜ በሕይወታችን ውስጥ የፅናትና የማሸነፍን ትርጉም በሙሉ ማንነታቸው የሚያሳዩን አስደናቂ ሰዎችን እንገናኛለን። ለእኔ ኢዘዲን ፈድሉ (Ezedin Fedlu) ከእነዚህ ብርቅዬ ሰዎች አንዱ ነው።

ከኢዘዲን ጋር አብሬ የመስራት እድል የነበረኝ በመሆኑ ስለ እሱ ሙያዊ ብቃት፣ ቁርጠኝነት እና አስተሳሰብ ብዙ ማለት እችላለሁ። እሱ ሁልጊዜ እንደሚለው አካል ጉዳተኛ ሳይሆን "በሌላ መንገድ የተዘጋጀ" (Enabled in a different way) ነው። እናም በጋራ በሰራንባቸው ጊዜያትም ሆነ በሕይወት ጉዞው ይህንን እውነት በተግባር አሳይቶናል።

ከአዲስ አበባ ተነስቶ ያሉበትን እንቅፋቶች ሁሉ በመሻገር፣ ዛሬ በስዊድን ውስጥ ከVolvo Cars ጋር እስከመስራት የደረሰበት መንገድ እውነተኛ የፅናትና የስኬት ማሳያ ነው።

ነገር ግን ኢዘዲንን የበለጠ ልዩ የሚያደርገው የደረሰበት የላቀ ደረጃ ብቻ አይደለም፤ በመንገዱ ላይ ያለው መልካም ልቡ እና ለሌሎች ያለው ግድተኝነት እንጂ።

ከመነሻው ጀምሮ እስከዛሬ ድረስ፣ በመንገዱ ያገኘውን ዕውቀት፣ ልምድ እና ማንኛውንም አጋጣሚ ለሌሎች ለማካፈልና ማህበረሰቡን ለማገዝ ወደ ኋላ ብሎ አያውቅም።

እንዲህ አይነት ድንቅ ሰዎች አክብሮታችንን ለማየት የግድ የመድረክ ሽልማት አያስፈልጋቸውም። አብሮአቸው ለሰራንና ለምናውቃቸው ሁሉ የሚሰሩት ሥራ እና የሚያሳዩት የሕይወት ጉዞ በራሱ ትልቅ ምስክር ነው።

Ezedin በአካል አብረን በሰራንበት ወቅት ላሳየኸኝ እውነተኛ የፅናትና ጥንካሬ ለሁላችንም ጥሩ ምሳሌ ስለሆንከን እና ያገኘኸውን ሁሉ ለሁላችንም ስለምታካፍለን ከልብ እናመሰግናለን!

#EzedinFedlu #Inspiration #Resilience #TechCommunity #Ethiopia #EnabledInADifferentWay #Leadership

Article of the day

"Should we rewrite it in Go?"

A payment-style service's p99 jumps from ~40ms to ~400ms during JVM GC pauses, and the backend team splits down the middle: half want Go for the consistent latency floor, half want Java 21 with ZGC to fix the pauses without a rewrite. This article is built to settle that argument honestly: with what each runtime actually documents, a decision framework, and a benchmark harness you can paste into a repo — so the deciding numbers are yours, not a blog's.

Read full article 👉 [LINK]

@devwitheyob
#TechVibe #ArticleOfTheDay #performance #Java #Go