Servicestack - Grouping like services together -

was wondering if there's recommended best-practice way of grouping similar services in what's becoming larger , larger project. of services can lumped in either dealing "pro" data or "amateur" data (the data goes way beyond simple flag in table, data totally different, different tables, on pro or amateur side.

i know can add routes classes...

/pro/service1 /am/service2

it looks can put dtos in namespaces....

what service.interface items (service , factory classes). put namespaces also?

finally, there way metadata page reflect these groupings? started go down road, services listed out in alphabetical order, , couldn't see route or namespace differences between service1 , service2.

thank you

if want, can split multiple service implementations across multiple dlls described on modularizing services wiki.

you can safely group service implementation classes nested folder groupings without having impact external services. changing namespaces on dto's can have effect if dto's make use of object, interfaces or abstract classes emit type info containing full namespaces.

in servicestack v4.09+ (now on myget) metadatafeature includes ability customize ordering of metadata page, e.g can reverse order of metadata pages with:

var metadata = (metadatafeature)plugins.first(x => x metadatafeature); metadata.indexpagefilter = page => {     page.operationnames.sort((x,y) => y.compareto(x)); };