Good design lends itself to being Easier To Change [ETC]. However, this principle of ETC tends to get ignored when it comes to API documentation and service validation. Here the tenants of Do Not Repeat Yourself [DRY] are often neglected leaving services with multiple files potentially spanning hundreds if not thousands of lines of code with copious amounts of duplication.
Development in services with monolithic validation engines and swagger documents then become a form of tech-debt. …
Enterprise microservices tend to be a combination of technologies. The objective of this post is to go over multiple approaches to different scenarios commonly found in enterprise JS services.
Before we get into the article, you can find most code samples inside this Github repository I threw together for this.
Senior Full-Stack developer building awesome things at Northwestern Mutual