Adding Route model and APIs

I agree that we need to use a different attribute for this. The way I see it, its just a prototype right now. It should pretty quickly evolve to store protocols (http, https, etc) pertaining to each "frontend" such that the router only listens to requests hitting that frontend with that particular protocol.

Also, we might decide to store multiple aliases for a given service in the same resource (and modify the the attribute type to an array) in which case, "Name" would no longer be appropriate anyways.