Update functional-vs-imperative-programming.md (#43152)

Author: azarboon

docs/standard/linq/functional-vs-imperative-programming.md

@@ -39,6 +39,8 @@ The primary reason to implement functional transformations as pure functions is
 - Easier reiterative development. Because the code is easier to refactor, changes to design are often easier to implement. For example, suppose you write a complicated transformation, and then realize that some code is repeated several times in the transformation. If you refactor through a pure method, you can call your pure method at will without worrying about side effects.
 - Easier testing and debugging. Because pure functions can more easily be tested in isolation, you can write test code that calls the pure function with typical values, valid edge cases, and invalid edge cases.
 
+For the reasons outlined above, functional programming is well-suited to the microservices architectural style.
+
 ## Transitioning for OOP developers
 
 In traditional object-oriented programming (OOP), most developers are accustomed to programming in the imperative/procedural style. To switch to developing in a pure functional style, they have to make a transition in their thinking and their approach to development.