Thanks Julius, but our DLL does all of the following, as well as compiling on our build server to work in our mobile app, in Docker Containers, and in Microsoft Azure -  it's more effective to retain complex business rules in a .NET library so that it can be used on a much wider basis. Also, .NET is easier to maintain in the sense that adding any new barcode format to the DLL updates all of our environments, not just the Cache one. We're into microservices in a big way, Cache is just our facade pattern entrypoint to the whole distributed system. Alot of the business rules tranlation is done simply by exchanging JSON at the microservice REST endpoints (we've also got a QR code Server in a docker container that's standalone and accessible by anything via a REST endpoint), however somtimes it's easier just to slap in a DLL as per the above question. Also, a lot of our team's expertise is tied up in .NET technologies so quite often a .NET solution is quicker and easier than passing the technology transfer information to the Cache developers. Thanks though.

Thanks, Dmitry, you're a hero!

I'm actually the .NET developer on the project, I passed your answer to the Cache developer and he's over the moon with delight!

Thanks Adam!!!