Hi everyone,
I’ve been working on larger C# applications where business logic tends to grow over time, and I’m trying to find patterns that help keep the codebase understandable and maintainable.
In my work with Funnelsflex, we often deal with workflows and systems that evolve as requirements change, and structuring code in a clear way has made a big difference in reducing bugs and onboarding new developers.
I’d like to know:
What architecture patterns (e.g., CQRS, Domain-Driven Design, layering) do you use for organizing business logic?
How do you manage complex decision logic without creating large, hard-to-read methods?
Are there specific conventions you follow to keep logic testable and reusable?
Looking forward to hearing practical experiences and patterns that have worked well for you. Thanks in advance!
Sam HobbsPosted Jan 20, 2026, 2:41 AM
You posted a similar question a couple of days ago. I am still unclear about what you are looking for.
Perhaps you need to use AI. An AI system can be trained for the specific domain you are working with.
Older versions of AI used Knowledge Bases. They are not as sophisticated as current AI technology but they might be all you need. A Knowledge Base is a database of logic. You can search for information about Knowledge Bases.
I found the following article. It might be relevant. Note that IBM has been doing that type of thing for about as long as anyone else.
Decision Modeling: Decision Logic
https://community.ibm.com/community/user/blogs/james-taylor/2023/11/16/decision-modeling-decision-logic
As I indicated IBM has been doing AI type stuff for about as long as anyone else. Their Watsonx is designed to help businesses. There are many other AI assistants that are popular, such as Google Gemini in Google Workplace.