Although planning helps with initial application design, Sisk’s architecture does simplify extending APIs, simply adding new routes as necessary. Starting with a well-structured application, new routes can be added with minimal disruption while ensuring code remains understandable. This is an important feature, as it ensures your applications and APIs are able to respond to new demands from users.
Routes, requests, and responses
Routes don’t need to be static. They can be dynamic and based on parameters set by other parts of an application or other user inputs. So, for example, if you’re using Sisk to provide access to an online catalog, you can have one route that starts at the root of the catalog, dynamically adding routes to pages inside the catalog.
Two key elements are associated with a route: requests and responses. Requests are received by Sisk and their URLs are matched to the router. At the same time, payloads are attached to a request object, ready for processing by the code associated with the route. Query strings aren’t matched, as they’re part of the request payload.
