Everyone gets so caught up in the terminology "micro" "macro" . The real value in what the microservice movement brings to the table is the push for well defin

Everyone gets so caught up in the terminology "micro" "macro" . The real value in what the microservice movement brings to the table is the push for well defined contracts between components before writing any code. But any good software engineer/architect knows the value of documenting design, so this should not come as as surprise. When considering only production systems, anybody that has a nightmare microservice deployment that is unruly to upgrade, version, or maintain always had some story about getting to market in record time before hand. Shipping services as quickly as possible to get the feature out the door without considering the downstream impact. (my absolute favorite... "we can solve auth later with a microservice in a container") I don't care if you have micro, macro, monolithic, or (pick a buzz word) architecture. If its not designed properly, it will always be a nightmare.