3 ms·
After a few more years where you have to scale these systems and redesign what services do and create competing ones that exist in parallel, you may find yourse
by stevebmark 4y ago
After a few more years where you have to scale these systems and redesign what services do and create competing ones that exist in parallel, you may find yourself back in support of non-descriptive names.
- pbreit 4y agoPremature optimization....
- stevebmark 4y agoMaybe, except there's not much downside. You also save significant time, because engineers trying to come up with the name of a service can be a drawn out and painful exercise, especially if it's a new service where you won't know its full responsibilities and boundaries until it's been used and built on for a significant time in production. I've seen so much time wasted with engineers trying to name services descriptively, especially when a similar service already exists.