What is the difference between convention-based routing and attribute routing? When would you use each?

in simple word convention routing: global route setup which is in rout cofig attribute route: custome route setup on controller ot action method

Convention-Based Routing Definition: Defines routing patterns in a central RouteConfig file (e.g., routes.MapRoute in RouteConfig.cs). Configuration: Routes are applied globally, based on predefined patterns. Flexibility: Less flexible for complex or specific scenarios. Readability: Routes are separated from controllers/actions, making them harder to trace. When to Use: Simple, consistent routing patterns across the application. Legacy MVC applications. Attribute Routing Definition: Defines routes directly on controller actions using attributes (e.g., [Route("api/products/{id}")]). Configuration: Routes are defined locally on controllers and actions. Flexibility: Highly flexible, allowing specific, fine-grained route definitions. Readability: Easier to trace routes as they are defined alongside the actions. When to Use: APIs and complex routing scenarios. Applications requiring custom routes for specific actions. Projects with microservices or RESTful services.