First of all, the style of Flask is based on frameworks such as SpringMVC, which uses decorators for routing. Take Java as an example

@Controller @RequestMapping("/") public class Index { @RequestMapping(method = RequestMethod.GET) public String index() { System.out.println("index called"); return "index"; } }

SpringMVC has been used in many commercial applications, so there is a market for this loose routing model.
Django has learned from the DRY principle (Don’t repeat yourself (DRY)) of Rails, so the default is more preferable to the configuration.

From the perspective of routing, I personally feel that Django is more flexible. If you are familiar with regular expressions, it is easy to change the routing of a URL, but it is a little troublesome in flask.

From a practical perspective, Django is heavier, Flask is lighter, Django performance is worse, Flask is better, Django documentation is better, Flask is worse, many people complain that Django ORM is terrible, Flask uses sqlalchemy by default, which is basically the standard of python ORM .

Anyway, each has its own merits. It’s hard to say which method is better in terms of Url routing. It depends on personal habits.

Personally, I think it depends on the size of the website. If the website is small, the two are similar.Flask优雅点，但是网站规模大了，一定是Django’s centralized routing management is better.