Muhammed Swafuvan’s Post

One reason why I love Vertical Slice Architecture (VSA): With VSA, I'm putting code, that relates together, in one file. The benefit of VSA is low coupling between slices and high cohesion inside slices. Even if C# doesn't force me into ordering of dependent code like F# does (which is a good thing), I can do this inside the slice code file. That way, I have a clear rule where to put what inside the slice code file. #csharp #dotnet #architecture

I read a Medium post today and came across this amazing illustration of S.O.L.I.D principles and Clean Architecture. I’ve seen similar diagrams before, but this one really nails it! Understanding these principles can greatly improve the quality and maintainability of our projects. Here are some key points highlighted in the image: • Single Responsibility: Each class or module should have only one reason to change. • Open/Close: Software entities should be open for extension but closed for modification. • Liskov Substitution: Objects of a superclass should be replaceable with objects of a subclass without altering the program’s correctness. • Interface Segregation: Clients should not be forced to depend on interfaces they do not use. • Dependency Inversion: High-level modules should not depend on low-level modules. Both should depend on abstractions. Big thanks to the author of the Medium post for creating such a clear and helpful visual! 🌟 #SoftwareEngineering #CleanArchitecture #SOLIDPrinciples #Coding #BestPractices #SoftwareDevelopment

Dive into the world of software architecture as I explore the intricacies of Monolithic Architecture and Service-Oriented Architecture (SOA). Whether you're a budding developer or a seasoned tech enthusiast, this read offers valuable insights into the pros and cons of each architectural style, helping you make informed decisions for your next project. Check it out and share your thoughts! 🌐 #SoftwareDevelopment #MonolithicArchitecture #ServiceOrientedArchitecture #TechInsights #MediumArticle #Programming #SoftwareEngineering

Here’s how I interpreted SOLID principles from Clean Architecture by Robert C. Martin (Uncle Bob) Single Responsibility Principle: - A module or class should be responsible for one and only one actor (a group of people who want the system to be changed in the same way). - Elements that tend to change for the same reasons should be grouped in the same package or module. - Set architectural boundaries by identifying the axis of change (potential areas or dimensions of a system where changes are most likely to occur over time, e.g., business rules, UI, external systems). Open/Closed Principle: The goal is to make systems easy to extend and minimize the impact of change. This can be achieved by separating things that change for different reasons (SRP) and using dependency inversion to isolate the change. Liskov Substitution Principle: LSP can and should be applied at the architecture level. A system should have reliable interfaces that are substitutable. A single violation of LSP can pollute the architecture of the system with complex mechanisms. Interface Segregation Principle: There shouldn't be a dependency on a module containing more than you need. This leads to unnecessary recompilations, redeployments, and failures you don't need. Dependency Inversion: Avoid dependency on concrete implementations of volatile and actively developing modules. Rather, rely on less volatile interfaces. #SOLID #SoftwareArchitecture #CleanArchitecture

Learning and building my skills in Entity-Component-System (ECS) architecture! Here’s a ComponentManager I wrote in C++ for a personal project.

A short video to summarize the kubernetes architecture and each component - #kubernetes

🚀 🚀 🚀 Exploring New Horizons: Vertical Slice Architecture and Modular Monoliths! 🚀 🚀 🚀 After extensive experience with Clean Architecture, I’m excited to share my recent exploration of Vertical Slice Architecture (VSA) and its impact on modern software design! 🔹 Vertical Slice Architecture (VSA), utilizing the REPR (Request, Endpoint, Response) design pattern, has truly impressed me with its simplicity and effectiveness. By structuring features into vertical slices, it facilitates a clear separation of concerns and streamlines the development process. While VSA provides an elegant solution, I anticipate challenges in managing and scaling as projects grow. Having already navigated the concepts of Modular Monoliths, I’m keen to see how VSA can complement and enhance my architectural practices. For those who have worked with VSA or have insights to share, I’d love to hear your experiences! #SoftwareArchitecture #VerticalSliceArchitecture #CleanArchitecture #ModularMonolith #Innovation #Programming #TechTrends

Required to watch "Vertical Slice Architecture isn't Technical" from Derek Comartin https://lnkd.in/e5FAYnns #systemdesign #softwarearchitecture #programming #eventdriven #eventsourcing #cqrs #eventmodeling

🔵 Hexagonal Architecture or should I say "Ports and Adapters"? It's like a game of telephone, but with software architecture! Who knew hexagons weren't involved? Just make sure your code doesn't get tangled up like a phone cord from the 90s. 💌 Subscribe to get fresh news every day: https://0xcafe.news