JsonApiDotNetCore VS Audit.NET

Well, that might be true when implementing from the scratch, but using a standard often also means, that someone has implemented a well known library to get rid of the boilerplate and basic decisions.

I personally often use jsonapi.net[1], a C# implementation of JSONAPI. This supports OpenAPI/Swagger with swashbuckle, has a very good filtering implementation and together with Orbit.js[2] it is pretty much without having to decide many things...

[1]: https://www.jsonapi.net/

It's so powerful that it even allows you to establish relationships between operations within a single request, using something called local IDs. Work is progressing quickly on the atomic-operations branch. Check it out on Github if you want to follow along.

In our previous post we setup a basic JSON:API compliant API with the 4.0 release of the JsonApiDotNetCore framework. You can find the code we wrote under the part-1 branch on Github.

I’ve had great success using Audit.Net. It supports a variety of different data stores and I believe it logs things in a background thread…I could be wrong though. At any rate, I have been using it with the EF provider and a custom table. No issues thus far.

I've looked into this as well and kept seeing https://github.com/thepirat000/Audit.NET pop up. There's also this huge thing https://abp.io/ that has auditing as a component.

Sounds like you could use Audit.NET

Next, I started looking into different available options. I came across various libraries, compare them and finally I chose Audit.Net WebApi for the following reasons:

There are about a billion packages for accomplishing this, e.g. https://github.com/thepirat000/Audit.NET/tree/master/src/Audit.EntityFramework - for everyone reading this, please use tried-and-tested packages like that, instead of this yet-another-reinvention-of-the-wheel.