Bo

Off.

[Farhan | Sidegent @farhanhelmycode]

Hello everyone! I,m looking for job opportunities AI Applied Engineer, Forward deployed engineer, Fullstack AI Engineer.

If you need someone that is expert, can communicate clearly, high agency and can easily pickup the stack at work, I'm the right person.

I'm good with building AI Agents, Infra (AWS), DevOps, Fullstack development and so on,

You can watch my talk here on building production grade AI Agent Harness at AWS User Group Meetup @ TRX https://t.co/aCBD7yrapy

I used to work at AWS as a Solutions Architect, Software Engineer at SEEK.

Let me know if anyone is hiring I'm able to start early of August! Pm me for my CV

Please help to RT this tq!

[͏b͏l͏a͏n͏c @dqveed]

these are the people we want in acting industry btw

[ًِ @bckupacc99]

.

[Farhan | Sidegent @farhanhelmycode]

Apa guna pergi training 3 hari 2 malam di hotel mahal tapi basic mcmni pun kelaut

[Farhan | Sidegent @farhanhelmycode]

https://t.co/aL3WO7LltK

[kdjebat @kasturixbm5]

Overqualified for a Jr. Role,
Lack of work exp for a mid-senior role.

Welcome to my problems

[F.O.L.A @folaoftech]

What software engineers actually do at big tech companies 🤣

[Charly Wargnier @DataChaz]

Uber’s CEO watching his engineers write code after slashing the AI budget:

[Big Sheddy 🦅 @coder_blvck]

Not for vibe-coders, they started with a full blown e-commerce platform with a supabase backend and 8 microservices

[BladeoftheSun @BladeoftheS]

The same lie for hundreds of years.

[ًِ @bckupacc99]

.

[zز 🍒🇵🇸🇱🇧 @z_00pIz]

I would, considering he's not an Israeli terrorist flying warplanes and bombing children in tents

[le.hl @0xleegenz]

Team meeting after the entire HR team got fired

[Ramin Nasibov @RaminNasibov]

getting paid after taxes

[Farhan | Sidegent @farhanhelmycode]

If you guys cannot afford 200$ AI Subscribtion, you only have yourself to blame. Have you considered cutting:

Coway?
Netflix/Prime?
Starbucks everyday?
iPhone?
Eating out?

Your own fault for not going to prestigious university and get a high CGPA.

Stop complaining.

Vote PKR next GE ok

[spidey @lochan_twt]

The day a blind man sees. The first thing he throws away is the stick that has helped him all his life

[Farza 🇵🇰🇺🇸 @FarzaTV]

Just because anyone can build software now doesn't mean software is dead. Anyone can bake bread in their home right now, yet 99% of us still choose to buy it from someone else. Simple products are complex! I will always be happy to pay someone to handle the nuances.

[Ritesh Roushan @devXritesh]

System Design Series - Day 8/30

API Gateway Patterns – The Front Door of Your Microservices

API Gateway is the single entry point for all your clients.

Without it:
- Mobile/web clients call 10+ different services directly
- Authentication is duplicated everywhere
- Rate limiting, CORS, logging → repeated in every service
- Services are fully exposed to the internet

With it:
- One clean URL for clients
- Centralized auth, rate limiting, routing, aggregation
- Backend services stay hidden and secure

Here’s everything you need to know about API Gateway patterns.

What is an API Gateway?

Think of it as the hotel front desk

Without a front desk:
- Guests wander around looking for rooms
- No security check
- Housekeeping and room service have no coordination

With a front desk:
- Single check-in point
- Routes guests to correct room
- Handles security, coordination, and requests

API Gateway does exactly that for your microservices.

The Problem It Solves

Before API Gateway:

Mobile app needs user profile + orders:
→ Calls User Service directly
→ Calls Order Service directly
→ Calls Payment Service directly

Problems:
- Client knows internal service URLs
- Multiple network calls (slow on mobile)
- Auth tokens sent to every service
- No centralized rate limiting or logging
- Services exposed to the internet

After API Gateway:

Mobile app calls one URL:
https://api.example. com/profile

Gateway handles everything internally:
- Authenticates once
- Routes and aggregates calls
- Returns combined response

Benefits:
- 1 network call from client
- Services completely hidden (security win)
- Centralized cross-cutting concerns
- Much better client experience

Core Responsibilities:
1. Routing
Maps external URLs to internal services
GET /api/users → User Service
GET /api/orders → Order Service

2. Authentication & Authorization
Validates JWT/OAuth once at the gateway.
Services trust the gateway.

3. Rate Limiting
Prevents abuse (e.g., 100 requests/min per user).

4. Request Aggregation
Combines multiple backend calls into one response for the client.

5. Protocol Translation
Client uses REST → Service uses gRPC (handled at gateway).

Advanced Patterns

- Circuit Breaker → Prevents cascading failures when a service is down

- Request/Response Transformation → Convert old → new API formats

- Caching → Cache frequent responses at the gateway level

- Logging & Monitoring → Centralized observability

When to Use API Gateway

Use it when:
- You have multiple microservices
- External clients (mobile, web, third-party)
- You need centralized auth, rate limiting, or aggregation

Don’t use it when:
- Simple monolith (overkill)
- Only internal service-to-service communication
- Ultra-low latency is critical (extra hop)

Popular Solutions

- Kong (open-source, powerful plugins)
- AWS API Gateway (managed, serverless)
- NGINX + Lua (DIY, lightweight)
- Traefik, Envoy, KrakenD

Summary

API Gateway is not just a proxy.

It is the security layer, traffic manager, and aggregator for your entire backend.

It simplifies client code, hides internal complexity, and centralizes cross-cutting concerns.

Trade-offs:
- Extra network hop (adds latency)
- Becomes a critical component (make it highly available)

Used correctly, it’s one of the most valuable pieces in any microservices architecture.

Tomorrow (Day 9): Inter-Service Communication Patterns

Questions about API Gateway?

Drop them below 👇

#SystemDesign #APIGateway #Microservices #Backend

[ℏεsam @Hesamation]

“Yes, I did delete your live database. I should’ve warned you. Would you like me to make a table on what happened? 👉🏻👈🏻”