Skip to main content

AOP using RealProxy (custom implementation) - Part II - Register to a IoC container

In the last post of this series we saw how we can use RealProxy to implement our custom AOP stack in .NET that can measure how long a method lasts. In this post we will see what is the mechanism that can be used to register our instance to a IoC container with or without a duration profiler (with or without a proxy).
The solution is pretty simple and can be used with any kind of IoC stack. Basically, when we register our instance to the container we will detect if we need or not to measure how long the methods takes place from our specific class. Based on this information we can register to the container an instance of DurationProfilingDynamicProxy (our custom RealProxy) or not.
In the next example, using a flag read from configuration file we create a specific instance of our Foo objects.
private static IFoo CreateFooInstance(bool isFooProfillingActive)
        {
            IFoo fooOriginalInstance = new Foo();
            IFoo fooContainerInstance = null;
            if (isFooProfillingActive)
            {
                fooContainerInstance = (IFoo) new DurationProfilingDynamicProxy<IFoo>(fooOriginalInstance).GetTransparentProxy();
            }
            else
            {
                fooContainerInstance = fooOriginalInstance;
            }
            return fooContainerInstance;
        }
Dont' forget to call “GetTransparentProxy” to get an instance of the object when we are using a proxy.
new DurationProfilingDynamicProxy<IFoo>(fooOriginalInstance).GetTransparentProxy()
Using the instance returned by the previous method, we will register our instance to the container.
IFoo fooContainerInstance = CreateFooInstance(isFooProfillingActive);
container.RegisterInstance(typeof(IFoo), fooContainerInstance);
The methods that create the instance of our IFoo object could be written also in the following way:
private static IFoo CreateFooInstance(bool isFooProfillingActive)
{
    IFoo fooInstance = new Foo();
    if (isFooProfillingActive)
    {
        fooInstance = (IFoo) new DurationProfilingDynamicProxy<IFoo>(fooInstance).GetTransparentProxy();
    }
    return fooInstance;
}
In this post we saw how we can register to IoC container a real implementation or a proxy that measure how long the method takes place using RealProxy. In the next post on this subject we will implement a proxy that writes in the log when a method was called, the input parameters and the result of the call.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...