Microservices are the cool, new way to build large software systems. The hype is everywhere, from the tech press to the hipster dude in the next cubicle. If you are building applications, you’ve probably felt at least some pressure to build them as microservices. However, if you’ve been in tech for very long, you’ve also seen a lot of fads come and go. You’re probably wondering if you are really choosing microservices for good reasons.
While it is not an exhaustive list everything from interacting with others to interacting with databases, to changing specs mid project, and misunderstandings about how business works are covered. These are the sort of critical mis-communications and non-optimal behaviors that distinguish a less experienced and less professional developer from those that have played the game a while and gotten some life experience. Being aware of these will help improve your employer’s (and fellow coworker’s) perception of you, as well as steer you away from problems that can cause you grief later.