My Premise: I’d really like to keep my services as small as possible, grouped by service name
I thought i would be able to create multiple services with the same name e.g.
s := res.NewService("users"), where one service handles creating, listing and updating a user and another service handles things like grouping, accounts etc… with the goal of keeping them small and manageable rather than ever growing macro services.
When i tried to create a 2nd service with the same name I get errors about conflicting service names, is that expected?
identity.create, identity.$id, identity.set
group.create, group.$id, group.set
what I’ve had to do is switch things around a bit, which while it does work, it doesn’t really feel right.
this is how i have had to do it, so far, but Im now realizing that this is going to result in the same problem…
user.create, user.$id, user.set
user.create, user.$id, user.set <- these are creating groups for the users which don’t really communicate as well as they should
while this seems like a good solution it becomes problematic when I need another service for non user group stuff, like creating nested groups, managing group permissions etc…
lets say Im consuming another services API, facebook for example, if I call the service
e.g. facebook-friends, facebook-groups, facebook-activities etc… which I guess is another solution but I can’t help but wonder why I can just have multiple services with the same service name that manage different handlers.
if I were just using nats native subscriptions that’s how I would do it, but something in go-res is tell me no (it looks like its coming from mux?). which is causing me to have weird service names like
password which handles user authentication. I would much rather have 1 micro service called
auth which handles user authentication and another service called
auth which handles company authentication or SAML authentication.
Anyways I hope this doesn’t sound too negative, I didn’t intend it to be negative, I’m just trying to set patterns and figure out the best practice for doing it. how does the saying go,
“There are only two hard things in Computer Science: cache invalidation and naming things.”