Designing URL paths
Once you've selected a web framework, the next important decision to make is how to design the URL path structure for your application. Now, you might be wondering, why does a URL path structure matter for my application, as long as requests are handled as I want them to be handled? Well, how you structure URL paths can affect how your application is designed.
Let's say you have a discussion forum application that deals with forums, topics, and posts. Each forum, such as Ruby Programming Books, can have topics such as Which is the Best Ruby Programming Book?, and each topic can contain many posts from the members of the forum with their thoughts on that topic. There are many possible ways to design a URL path structure for such a forum application.
You could call one approach the flat approach, where each separate type has its own top-level path. For example, you could have the following three URL paths for the forum application:
/forums...