ServiceStack VS JsonApiDotNetCore

That's a bit handwavy, which of the major ServiceStack features listed on https://servicestack.net homepage does masstransit do? Ok if you just need what's in masstransit & aren't to up to speed with ServiceStack's latest featureset, but to suggest no-one else would find any of its productive features useful is unnecessarily dismissive.

Not sure if it's exactly what you are looking for but all of the things you mention are features of ServiceStack https://servicestack.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.