Disposable Instances Series
In the past few weeks I have published a set of four posts that deal with disposable instances. These posts describe in detail a working implementation that automatically disposes all the instances that are no longer needed, in a deterministic way. This solution works when we use Dependency Injection or
In the past few weeks I have published a set of four posts that deal with disposable instances. These posts describe in detail a working implementation that automatically disposes all the instances that are no longer needed, in a deterministic way. This solution works when we use Dependency Injection or Service Locator to create instances and we want to prevent, by design, leaks of expensive resources.
The posts started from a discussion on how to deal with a repository implementation, which is disposable by nature, and it evolved into a broader one, because the same challenges and approaches apply to any disposable type.
Even if I didn’t intend them from the beginning to be a series, these posts continue each other and describe the design of a component that may be part of the Application Software Infrastructure of any complex app. They include the problem description, the challenges, the different approaches which may be considered and implementation examples.
The posts are:
- Who Disposes Your Repository – where I describe the context and the challenges of dealing with a disposable Repository and Dependency Injection. In this post I also compare different alternatives of handling the dispose in a repository implementation
- Extending Unity Container for IDisposable Instances (1st approach) – here I detail the challenges of achieving automatic dispose with Unity Container and I describe one implementation approach with its pros and cons
- Extending Unity Container for IDisposable Instances (2nd approach) – here I continue the post above with another solution for extending Unity with this behavior. This implementation overcomes the shortcomings of the previous one, but raises some design concerns
- Disposing Instances when Using Inversion of Control – here I complete the solution by addressing the question of when the disposables are going to be disposed. I give a solution for defining a scope for any operation in any kind of app in a similar way as we have the Request in an web app
many solutions and discussions like the above are included in my Code Design Training
Image by: eteimaging / 123RF Stock Photo
Code Design for Predictability: Why You Should Hide the Frameworks
Software projects rarely collapse because of lack of talent. They collapse because complexity grows faster than it is controlled. When technical failure happens, the root cause is often unmanaged complexity. You have seen it: - Small changes become expensive. - Adding developers does not increase speed. - Deadlines move again
Designing Resilient Software Systems for the Energy Sector
Resilience is the primary requirement for software systems in the energy sector. These systems support critical operations such as grid balancing, energy trading, risk management, and asset management. Failure is not an option. Energy systems must operate continuously. Orders must always be processed. Data loss is unacceptable. Business processes must
How Delivery Architecture Enables Predictable Software Projects
Learn how to design software projects for predictable delivery using Delivery Architecture. Align Code Design, System Design, and Project Design to control complexity, reduce risk, and deliver on time and on budget.
Coding with Copilot on Top of Application Infrastructure
AI coding works best on top of strong Application Infrastructure. With clear structure, strict boundaries, and consistent design rules, Copilot and AI Agents generate cleaner, more predictable code. Architecture guides the AI, not the other way around.
Integration Gateway for External Systems
An Integration Gateway isolates your system from external changes and failures while standardizing communication. This article explores a Code Design approach using Contract-First Design, Pluggable Applications, and Clean Architecture for reliable and maintainable software integration.
Viewing Software Projects Through an Activities Network
Learn how Activities Network Diagrams improve Project Design and Project Management by clarifying dependencies, reducing cost, and increasing predictability of delivery, budget, and quality in complex software projects.
Drawing from our extensive project experience, we develop training programs that enhance predictability and reduce the cost of change in software projects.
We focus on building the habits that make developers adopt the industry best practices resulting in a flexible code design.
