Articles.

You can keep new features, changes, and alternative behaviors of your application “dormant” in production so that by turning on run time “switches”, only you and your testers can experience these behaviors. You control which new or experimental behaviors are switched on of off for the whole world.

Some advice is not even wrong. We try to find out who this article was supposed to be written for, whether this is valid question, how to ask better questions, and how to get better advice.

Any architectural style has trade-offs: strengths and weaknesses that we must evaluate according to the context that it's used. This is certainly the case with microservices.