> One key part is that naming is important. This is always a fight I am willing to take. Acronyms, fantasy names, names of teams or legacy names that does not r

> One key part is that naming is important. This is always a fight I am willing to take. Acronyms, fantasy names, names of teams or legacy names that does not represent the functionality of the micro-service plague many companies. > If you will not name a method "Jimmy" or a local variable "Galactus", why developers are naming their micro-services in such a bad way? There was a post on the front page today about the "principle of least astonishment." It could not be more applicable than this example. For those that missed it => https://wiki.c2.com/?PrincipleOfLeastAstonishment https://wiki.c2.com/?PrincipleOfLeastAstonishment