Bogus VS Ocelot

Bogus NuGet package is fake data generator which can be helpful for populating tables in a database and testing purposes. If a database is not used and Bogus populates list of data each time an application runs, the data is random, never the same. Also, the random data generated by Bogus may not meet a developer’s requirements.

A list is populated with NuGet package Bogus.

Other project either mocked data using NuGet package Bogus or a json file.

That reminds me of Bogus which also generates dummy data that I've been using for sometime now.

To do all this you need test though...and that's where ]Bogus](https://github.com/bchavez/Bogus) and Auto Bogus come in handy. They both generate semi random test data that you can use to populate whatever method you've decided to use. You can setup rules so for specific fields, they have built in generators for common things like names and addresses. Auto Bogus can be used to populate large/complicated objects with data automatically (it can be slow if you don't use .WithRecursiveDepth() or.WithTreeDepth() )

Bogus - For creating fake data Verify - Snapshot testing for .NET MELT - For testing ILogger usage Stryker - Mutation Testing for .NET TestContainers - run docker programmatically in integration tests

To keep things interesting Bogus library is used to create a Person instance.

Usage with mocked data using Bogus NuGet package.

I would say the issue is either a general issue with how Revit loads the addin, or maybe an issue with conflicts in your transitive dependencies. You can do some tests to try to figure out which. Try making a barebones Revit addin that uses a library that has no dependencies and isn't likely to be used in Revit. I'd suggest Bogus, you can use it generate a few pieces of test data and log them/display in the UI/whatever. If that works, then it would appear that Revit is fine with your addin having dependencies (which I would expect).

Sounds like you need some kind of ETL. The only dotnet library I know, which supports request aggregation, is Ocelot (https://github.com/ThreeMammals/Ocelot). But I doubt it is the only one out there.

They seems to recommend https://github.com/ThreeMammals/Ocelot

Ocelot Github Nuget: Install-Package Ocelot -Version 17.0.0

Ok, now that you created you Web API, it's time to work on your API Gateway. Start by adding the Ocelot package to your Gateway project:

Discovered Ocelot and it looks like a good place to start, so you have any thoughts on that?

I'd look for an open-source gateway using the programming language that you're familiar with. I was working multiple times with the custom API GW (including building my own for fun), and if you're familiar e.g. with C# take a look at this one https://github.com/ThreeMammals/Ocelot or even better https://github.com/microsoft/reverse-proxy If you need to build something really custom, there's a small chance that you will find a plug & play solution.

Lol, i guess your answer explains a lot about relevant knowledge into web architecture

Eg. Ocelot - https://github.com/ThreeMammals/Ocelot