Strategies for Managing Custom Requests in .NET Core Projects

Question

Hi everyone,

My team and I are starting a new project.

We plan to develop and sell this project to multiple companies. While we will be the sole developers, we'll incorporate requests from these companies into the project.

The project will undergo a general development period where updates are universally applied to all users. However, some users may have specific requests for particular modules.

We're currently exploring how to balance broad updates with these unique requests.

Key Point:

General updates must not interfere with specific modifications. Nevertheless, these updates should be accessible to all clients.

Example:

Consider our BlogController: By default, only administrator-approved messages are published. However, one of our clients might request that posts go live only after SMS verification.

Our challenge is to ensure that updates to the BlogController benefit all users while maintaining the integrity of specific requests like SMS verification.

Technologies we'll use:

• .NET Core
• Angular
• PostgreSQL
• Modular Monolith Architecture

Your insights on managing these aspects would be highly valuable.

Answer 1

you will want to use the plugin design pattern. You will also probably want to replace the simple DI support in asp.net with a more configurable one.