G.Jonathan

First international award!!! Yassssssssssssssssssssssssss

𝗗𝗮𝘆 𝟲𝟲 𝗼𝗳 #𝟭𝟬𝟬𝗗𝗮𝘆𝘀𝗢𝗳𝗦𝘆𝘀𝘁𝗲𝗺𝗗𝗲𝘀𝗶𝗴𝗻 — 𝗘𝘃𝗲𝗻𝘁-𝗗𝗿𝗶𝘃𝗲𝗻 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗘𝘃𝗲𝗻𝘁-𝗗𝗿𝗶𝘃𝗲𝗻 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 (𝗘𝗗𝗔) is a design pattern where services communicate by producing and consuming events. Instead of directly calling another service, a service emits an event when something happens. Other services listen for that event and react accordingly. This creates loose coupling. Services don’t need to know about each other — they only need to know about events. For example, when a user places an order, an Order Service can emit an “Order Created” event. A Payment Service, Notification Service, and Inventory Service can all react to that event independently. Think of it like a restaurant. When a waiter places an order on the board, it signals that something has happened. The kitchen starts cooking, the drinks station prepares beverages, and the cashier prepares the bill — all based on that one event. No one needs to directly tell each station what to do. That’s the power of event-driven systems. They improve scalability, flexibility, and allow systems to evolve independently. But they also introduce complexity in tracking flows and debugging. #SystemDesign #DistributedSystems #BackendEngineering #100DaysOfSystemDesign

@TosinOlugbenga @GammsApp 👏👏👏

I need few people to please help review @GammsApp landing page we newly deployed. Based on the feedback from my brother Mainstack CEO earlier in the week, when you click the link, you no longer hit the auth wall as a visitor. Your feedbacks will be appreciated. Gamms.app

@Akintola_steve @upstash This is niceee

Good morning, First time testing Redis? You all can try out @upstash — Free Redis, ready in minutes. Here’s all you need to do: ∙ Go to upstash.com . Create a free account ∙ Create a new Redis database ∙ Copy your connection string ∙ Connect & you’re good to go. No server stress, no bills.

𝗗𝗮𝘆 𝟲𝟱 𝗼𝗳 #𝟭𝟬𝟬𝗗𝗮𝘆𝘀𝗢𝗳𝗦𝘆𝘀𝘁𝗲𝗺𝗗𝗲𝘀𝗶𝗴𝗻 — 𝗞𝗮𝗳𝗸𝗮 𝘃𝘀 𝗥𝗮𝗯𝗯𝗶𝘁𝗠𝗤 (𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘂𝗮𝗹𝗹𝘆) Message queues are essential in distributed systems, but not all queues are the same. Two popular systems are RabbitMQ and Kafka, and they serve different needs. 𝗥𝗮𝗯𝗯𝗶𝘁𝗠𝗤 is a traditional message broker. It focuses on reliability, flexible routing, and task processing. Producers send messages, and consumers process them — messages are typically removed from the queue once consumed. It’s great for background jobs, notifications, or short-lived tasks. 𝗞𝗮𝗳𝗸𝗮 is more of a distributed event streaming platform. It keeps messages in a log for a configurable time, allowing multiple consumers to read independently at their own pace. Kafka is ideal for real-time analytics, event sourcing, and high-throughput pipelines. Think of it like a restaurant. RabbitMQ is like a waiter delivering orders directly to the chef. Once the dish is cooked and served, it’s done. Each order is handled individually. Kafka is like a big order board where every station can see the order history and pick orders whenever needed. The orders stay on the board for a while, letting multiple chefs or stations process them independently. Choosing between them depends on whether your system needs task queues or event streams.

Help others grow.

@Limtech001 Hi Temi let me send you the mic, would love to hear from you

@beardedtech_guy Security can be done on both frontend and backend E.g XSS scripting, frontend can also validate input same as backend. I believe there’re work to do on the backend

It’s about time soon twitter.com/i/spaces/1kKzD… Reserve your seat!

@soy_leroy_ Big man! Happy birthday

Happy birthday to me. 🎉🎂 Thank you God for keeping things running smoothly. 🙏🏾

If there’s a Functional requirement then it’s not exactly compulsory What happens when the backend needs to start same time the Deisgn team is starting? So whats more important is getting an understanding of what to deliver sha

Do bad people know they are bad ? Or they think they’re doing great?

@NayteExploits Thank youuu

@beardedtech_guy That's rare Happy for you Jonathan

The point where you get consumed by your work because you enjoy doing it.

So I am a psychopath? 🤣

For some reason I still like using vite 😅 Be like I be old school

Ws!

@NayteExploits Lol yeah. I have a job I work and I enjoy it a lot

@beardedtech_guy Is it even work if you are enjoying it

I want my network to be so wide that I can always have someone to call when somebody needs a hand.