I'm Majdi, As a Software Engineer I am trained and experienced in designing, constructing, testing and supporting systems.
My main focus is building fast, accessible, and engaging apps that resolve problems and users enjoy.
I have a strong foundation in advanced software development, system design, and project management. My academic journey at INSAT honed my technical expertise and analytical skills, allowing me to tackle complex software challenges.
Currently, I am working as a Solution Architect at Sanofi, where I design and implement innovative technology solutions that align with the company's strategic goals. In this role,
I collaborate closely with cross-functional teams to translate business requirements into scalable, efficient, and secure systems.
My work involves ensuring the seamless integration of various technologies, optimizing performance, and maintaining a focus on sustainability and future growth. This position allows me to leverage my expertise in software engineering while driving impactful solutions in the healthcare industry.
If you’re diving into microservices or looking to scale your systems, you’ve probably heard of Event-Driven Architecture (EDA). It’s a buzzword for a reason — EDA is a game changer when it comes to building responsive, scalable applications. But what exactly is it, and how does it stack up against more traditional approaches? Let’s break it down.
Every streaming system, every queue, every webhook integration eventually meets a producer faster than its consumer. Backpressure is what decides whether that moment is a graceful slowdown or a cascading outage.
Conway's Law says systems mirror the communication structure of the organizations that build them. Domain-Driven Design says a bounded context should mirror the domain. Most of the time, the domain loses that argument.
Both are called 'events.' Both get published to a broker. That surface-level similarity is exactly why teams keep publishing one where they should be publishing the other, and why the mistake is so hard to notice until a schema change breaks three unrelated services.