Comments by "Michael Stover" (@michaelrstover) on "DRY Software Patterns u0026 Microservices" video.

  1. It seems like a great reason to not use microservices unless absolutely forced because of organization scaling issues. A small company with 6 developers shouldn't be doing this to themselves.
    2
  2.  @ModernSoftwareEngineeringYT  This seems like an excellent argument for not making such fine-grained microservices. It seems like if you're drawing boundaries around the problem domains, both the order history and order display are within a single problem domain, and so they would share the representation of "Order".
    1