InfoQ Homepage Loose Coupling Content on InfoQ
Articles
RSS Feed-
/articles/consistency-coupling-complexity/en/smallimage/consistency-coupling-complexity-s-1628577348640.jpg)
Consistency, Coupling, and Complexity at the Edge
Successful use of a microservices architecture requires maintaining a clear separation of concerns in the various layers and by employing design principles best suited to each layer. While RESTful API design has become the standard for microservices, it can cause problems at the UI layer. Alternatives such as the Backend-for-Frontend pattern using GraphQL can provide better separation of concerns.
-
/articles/NDepend/en/smallimage/articlelogo.jpg)
Cut off wrong dependencies in your .NET code
Patrick Smacchia advises developers to treat each namespace in an application as a component, and make sure there are no dependency cycles between your components. He claims that by abiding by this simple tenet, the structure of a large application can’t diverge to the monolithic block of spaghetti code base that seems to be the rule more than the exception in enterprise professional development.
-
/articles/ninject10-released/en/smallimage/logo.png)
Nate Kohari on Releasing Ninject 1.0
Ninject is touted as a lightning-fast, ultra-lightweight dependency injector for .NET applications. Helping developers split applications into a collection of loosely-coupled, highly-cohesive pieces, and then glue them back together in a flexible manner. Using Ninject to support your software's architecture, your code will become easier to write, reuse, test, and modify.