Service Middleware Considerations

Service Middleware considerations

Within a middleware, you can use the container to access the registered services. This enables you to have full control for implementing the necessary logic in your global middleware, but there is one limitation. If you call the same service that the middleware is using, it will result in an infinite loop within your middleware.

container.middleware.add('KeyService1', (next, context, args) => {
  const { container } = context;

  // Get the services 
  const service1 = container.get('KeyService1');
  const service2 = container.get('KeyService2');

  // Infinite loop error (KeyService1)
  const random = service1.getRandom();

  // Calling a method or function from any other service, will not
  // generate an infinite loop.
  const uniqId = service2.getUniqId();
  return next(args);
})

To avoid the infinite loop, you can use the proxyMiddleware option to disable the middleware proxy:

container.middleware.add('KeyService1', (next, context, args) => {
  const { container } = context;

  // Get the services
  const service1 = container.get('KeyService1', {
    proxyMiddleware: false,
  });
  const service2 = container.get('KeyService2');

  // Now we can use the service1 without the infinite loop
  const random = service1.getRandom();
  const uniqId = service2.getUniqId();

  return next(args);
})