This is an awesome article. We focus so much on the implementation details and learning how to make things work that we put it right at the heart of our applications instead of trying to push those details to the edges as your diagram illustrates.
In the .NET world, once Azure got big you'd see applications where every single class was in some way tightly coupled to ServiceFabric. Once that's done it's really hard to undo.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is an awesome article. We focus so much on the implementation details and learning how to make things work that we put it right at the heart of our applications instead of trying to push those details to the edges as your diagram illustrates.
In the .NET world, once Azure got big you'd see applications where every single class was in some way tightly coupled to ServiceFabric. Once that's done it's really hard to undo.