If you’ve read the previous articles on Function Monkey you may be wondering if you always need a command handler. Sometimes you may want to accept a request into the system (for example via HTTP) and that pass that request off for further processing. For example the HTTP data can be accepted and then the data (“command”) can be put on a queue for processing. This allows the potential scale-out of the function that processes queue messages to improve the overall throughput of the system.
Take the following example that allows an invoice to be submitted via HTTP. The submitted invoice is validated before simply being returned from the SubmitInvoiceCommandHandler. The output of the handler gets sent to a storage queue called “invoices”. Then we have a queue storage trigger creating and handling the ProcessInvoiceCommand.
using System.Net.Http;
using System.Threading.Tasks;
using AzureFromTheTrenches.Commanding.Abstractions;
using FluentValidation;
using FunctionMonkey.Abstractions;
using FunctionMonkey.Abstractions.Builders;
using FunctionMonkey.FluentValidation;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Logging;
namespace FunctionApp2
{
public class SubmitInvoiceCommand : ICommand<SubmitInvoiceCommand>
{
public string Description { get; set; }
public decimal Amount { get; set; }
}
public class SubmitInvoiceCommandValidator : AbstractValidator<SubmitInvoiceCommand>
{
public SubmitInvoiceCommandValidator()
{
RuleFor(x => x.Description).NotEmpty();
RuleFor(x => x.Amount).GreaterThan(0);
}
}
public class SubmitInvoiceCommandHandler : ICommandHandler<SubmitInvoiceCommand, SubmitInvoiceCommand>
{
public Task<SubmitInvoiceCommand> ExecuteAsync(SubmitInvoiceCommand command, SubmitInvoiceCommand previousResult)
{
// We are not actually "handling" anything here, the handler is just returning the sam command
return Task.FromResult(command);
}
}
public class ProcessInvoiceCommand : ICommand
{
public string Description { get; set; }
public decimal Amount { get; set; }
}
public class ProcessInvoiceCommandHandler : ICommandHandler<ProcessInvoiceCommand>
{
private readonly ILogger Log;
public ProcessInvoiceCommandHandler(ILogger log)
{
Log = log;
}
public Task ExecuteAsync(ProcessInvoiceCommand command)
{
Log.LogInformation($"Processing invoice {command.Description} {command.Amount}");
return Task.CompletedTask;
}
}
public class FunctionAppConfiguration : IFunctionAppConfiguration
{
public void Build(IFunctionHostBuilder builder)
{
builder
.Setup((serviceCollection, commandRegistry) =>
{
serviceCollection.AddTransient<IValidator<SubmitInvoiceCommand>, SubmitInvoiceCommandValidator>();
commandRegistry.Register<SubmitInvoiceCommandHandler>();
commandRegistry.Register<ProcessInvoiceCommandHandler>();
})
.AddFluentValidation()
.Functions(functions => functions
.HttpRoute("v1/SubmitInvoice", route => route
.HttpFunction<SubmitInvoiceCommand>(HttpMethod.Post)
.OutputTo.StorageQueue("invoices"))
.Storage(storage => storage
.QueueFunction<ProcessInvoiceCommand>("invoices"))
);
}
}
}
If we POST the JSON { "Description" : "NAS", "Amount" : 1000 } we get the following (abridged) output:
Executing HTTP request: {"method": "POST", "uri": "/api/v1/SubmitInvoice"}
Executing 'SubmitInvoice'
Executed 'SubmitInvoice'
Executing 'StqFnProcessInvoice' (Reason='New queue message detected on 'invoices')
Storage queue trigger function StqFnProcessInvoice processed a request.
Processing invoice NAS 1000.0
Executed 'StqFnProcessInvoice'
At the moment the SubmitInvoiceCommandHandler is not doing anything useful, it’s just passing the command back out so it can be output to queue storage.
With Function Monkey you can do away with the command handler in these cases.
One way to do this is when configuring the function app by adding the NoCommandHandler() option in the build method. This means that the SubmitInvoiceCommandHandler class can be deleted:
using System.Net.Http;
using System.Threading.Tasks;
using AzureFromTheTrenches.Commanding.Abstractions;
using FluentValidation;
using FunctionMonkey.Abstractions;
using FunctionMonkey.Abstractions.Builders;
using FunctionMonkey.FluentValidation;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Logging;
namespace FunctionApp2
{
public class SubmitInvoiceCommand : ICommand<SubmitInvoiceCommand>
{
public string Description { get; set; }
public decimal Amount { get; set; }
}
public class SubmitInvoiceCommandValidator : AbstractValidator<SubmitInvoiceCommand>
{
public SubmitInvoiceCommandValidator()
{
RuleFor(x => x.Description).NotEmpty();
RuleFor(x => x.Amount).GreaterThan(0);
}
}
public class ProcessInvoiceCommand : ICommand
{
public string Description { get; set; }
public decimal Amount { get; set; }
}
public class ProcessInvoiceCommandHandler : ICommandHandler<ProcessInvoiceCommand>
{
private readonly ILogger Log;
public ProcessInvoiceCommandHandler(ILogger log)
{
Log = log;
}
public Task ExecuteAsync(ProcessInvoiceCommand command)
{
Log.LogInformation($"Processing invoice {command.Description} {command.Amount}");
return Task.CompletedTask;
}
}
public class FunctionAppConfiguration : IFunctionAppConfiguration
{
public void Build(IFunctionHostBuilder builder)
{
builder
.Setup((serviceCollection, commandRegistry) =>
{
serviceCollection.AddTransient<IValidator<SubmitInvoiceCommand>, SubmitInvoiceCommandValidator>();
commandRegistry.Register<ProcessInvoiceCommandHandler>();
})
.AddFluentValidation()
.Functions(functions => functions
.HttpRoute("v1/SubmitInvoice", route => route
.HttpFunction<SubmitInvoiceCommand>(HttpMethod.Post)
.Options(options => options.NoCommandHandler())
.OutputTo.StorageQueue("invoices"))
.Storage(storage => storage
.QueueFunction<ProcessInvoiceCommand>("invoices"))
);
}
}
}
If we submit the same JSON request we get:
Executing HTTP request: { "method": "POST", "uri": "/api/v1/SubmitInvoice"}
Executing 'SubmitInvoice'
Executed 'SubmitInvoice'
Executing 'StqFnProcessInvoice'
Storage queue trigger function StqFnProcessInvoice processed a request.
Processing invoice NAS 1000.0
Executed 'StqFnProcessInvoice'
Even though we don’t have an explicit handler now for the SubmitInvoiceCommand, the validation still takes place.
Another option is to implement the marker interface ICommandWithNoHandler in the command and then you don’t need the .NoCommandHandler() option.
Other Function Monkey articles:
SHARE: