Maurice Kherlakian’s Post

What's your folder structure and architecture?? let's start with a fundamental concept: Model-View-Controller (MVC). This setup isn't just a fancy term; it's a practical framework that makes development smoother and projects more scalable and maintainable. But here's something often overlooked: the way we organize our project folders. It's not just about looks; it's about making things efficient and clear. A well-structured folder system lays down the groundwork for easier collaboration, simpler debugging, and smoother scalability.

Don't use Clean Architecture if: - You have a small, simple project - You are working on a tight deadline - You have limited resources or expertise Clean Architecture is a popular architectural approach. It separates the business logic from implementation details. It also promotes a modular and scalable approach to software development. However, it's far from a silver bullet for complex systems. There are certain situations where it's not the best choice. 1. 𝗪𝗵𝗲𝗻 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲 𝗮 𝘀𝗺𝗮𝗹𝗹, 𝘀𝗶𝗺𝗽𝗹𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 - Clean Architecture is excellent for complex systems - Not worth it for small systems (unnecessary complexity) - Can slow down your development process (initially) 2. 𝗪𝗵𝗲𝗻 𝘆𝗼𝘂 𝗮𝗿𝗲 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗼𝗻 𝗮 𝘁𝗶𝗴𝗵𝘁 𝗱𝗲𝗮𝗱𝗹𝗶𝗻𝗲 - Clean Architecture is an investment in the long run - Requires a decent amount of upfront boilerplate - It helps if you have previous projects to reuse 3. 𝗪𝗵𝗲𝗻 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲 𝗹𝗶𝗺𝗶𝘁𝗲𝗱 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀 𝗼𝗿 𝗲𝘅𝗽𝗲𝗿𝘁𝗶𝘀𝗲 - Easy to overengineer if you don't know what you are doing - Clean Architecture has a strict set of rules you need to follow - The main principle of Clean Architecture is dependency inversion - Requires an understanding of software design principles and patterns If you've been following me for a while, you know I love Clean Architecture. #clean_architecture #flutterdeveloper #dart

Clean Architecture Clean architecture isn't revolutionary. You need to follow one crucial principle: inner layers can't reference outer layers. Essentially, we're applying dependency inversion on the application level. Inner layers define abstractions, and outer layers implement these abstractions. You can package Clean Architecture across multiple projects. This is the most common approach with a Domain, Application, Infrastructure, and Presentation project. However, you can also group components for a single feature together. This is called a vertical slice, and it improves the cohesion of your design. What are the benefits of Clean architecture? - Modularity - Separation of concerns - Testability of business logic - Improved team productivity - Loose coupling of components #cleanArchitecture

As I was reading the book "Clean Architecture" by Robert C. Martin! , I wanted to share an insight on Duplication in code . Duplication can be a double-edged sword, with true duplication and accidental duplication being key distinctions. True duplication occurs when identical or very similar code exists in multiple places within a system, leading to maintenance headaches and increased risk of bugs. Now imagine two use cases that have very similar screen structures. The architects and developers will be strongly tempted to share the code for that structure. But should they ? Is that a true duplication or it is accidental? Most likely it is accidental. As time goes by the odds are that those two screens will diverge and eventually look very different. For this reason , care must be taken to avoid unifying them . Otherwise separating them later will be a challenge. As architects and developers, you will often run into this issues and your temptation will be to couple the use case as they have similar screen structure or similar algorithms or similar schemas . Be careful. Resist the temptation . First make sure the duplication is real ! #CleanArchitecture #CodeQuality #SoftwareDevelopment 🚀🔍

Software architecture is not a simple game. In a perfect world, it would look like the picture on the left. We start, apply great architecture and we are done. Next. But in the real world it is more like a tree. It grows over time. It changes what it looks like - in the beginning the tree is small and thin. We can easily give it direction. Over time it becomes harder and harder to change its core, but we can take care of it, water it, trim it and remove the dead parts. Sometimes the choices are very difficult. That's why it's so important to look at architecture holistically: ➡ know your domain in depth ➡ do not forget about infrastructure (it is one of anti-patterns) ➡ think about solution structure ➡ decide on your testing strategy ➡ think how often would you like to release your product ➡ do not forget that business is changing and so is your architecture "IT architecture is a profession of trade-offs: flexibility brings complexity; decoupling increases latency; distributing components introduces communication overhead." - Gregor Hohpe How do you approach architecture in your company? Share your thoughts in the comments below! 💬 #softwarearchitecture #softwaredevelopment

In a realm where change is the only constant, adaptability and agility are more than just buzzwords – they're necessities. That's where Composable Architecture comes into play, and we're here to guide you through its transformative potential. 🏗️💡 Why Composable Architecture, you ask? - It's like giving your tech stack superpowers – speed, flexibility, and scalability. 🦸♂️🦸♀️ - It empowers businesses to respond swiftly to market changes, much like a chess grandmaster anticipating moves. ♟️ - It fosters innovation, allowing you to mix, match, and experiment with components like a gourmet chef with ingredients. 🍳🌶️ Our blog post breaks down the complexities and showcases how Composable Architecture is not just a trend, but a pivotal shift in how we approach software development. 👉 Dive into our content and explore how Composable Architecture can revolutionize your tech strategy!

In one project, everything just worked. We added features effortlessly. The architecture guided us, but never hindered us. It was simple, not too much, but nothing missing. Everyone knew what to do. The architecture stood not in our way. It required only the necessary tasks—nothing more, nothing less. Unlike over-engineered projects, where you constantly deal with irrelevant complexities, or under-engineered ones, where you're overwhelmed by missing elements and workarounds. Simplicity is not randomly leaving out things. It's the right dosage, and achieving it feels awesome. Everyone wants software architecture to be fancy. Sometimes, it's just about doing the necessary things, like moving a couch. Do you know this feeling? #SoftwareArchitecture #Design #Simplicity

The Architecture Canvas is used in two different stages of the architecture design: 1- Identifying concepts (functional, non-functional and integration needs) The canvas helps collecting architecture requirements in a structured and systematic way. 2- Define modules Design the modules that implement the identified concepts. Designing an architecture is not a one-time event. It is a continuous process. The architecture must be iterated, cycling these two stages. #LogicaSys #outsystems

When thinking about clean architecture, if the first thing that comes to mind is the four-layer circle diagram, you might be missing its true essence. Clean architecture is not just about organizing modules; it's about enabling a large developer team to work together seamlessly. It ensures that everyone can work independently while maintaining an organized and optimized codebase. Clean architecture fosters collaboration and efficiency, making it much more than just a visual representation of module organization.