join-monster
JsonApiDotNetCore
join-monster | JsonApiDotNetCore | |
---|---|---|
3 | 7 | |
2,656 | 653 | |
0.2% | 1.2% | |
6.6 | 9.2 | |
1 day ago | 6 days ago | |
JavaScript | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
join-monster
-
Understanding TTFB Latency in DJango - Seems absurdly slow after DB optimizations even locally
GraphQL could be efficiently translated into SQL and things certainly try, but the only thing close to a "bulletproof" implementation I found was Join Monster (https://github.com/join-monster/join-monster) in NodeJS-land and even that I think is now mostly abandoned. GraphQL as a system was built assuming random-access to data stores is ~free because that's what Facebook has, but the rest of us don't :)
-
Ask HN: Nested Resources in REST/HTTP API URLs?
REST is not a strict specification and it's not a single implementation, you can just start doing it.
That said, I wouldn't recommend going the allow everything flexible resolver way like GraphQL: it's terrible for performance (eg. most APIs use N+1 queries unless you have something like https://github.com/join-monster/join-monster), the complexity of the codebase skyrockets and having to specify all the fields you want is not exactly ergonomic in most situations.
- GraphQL Is a Trap?
JsonApiDotNetCore
-
Ask HN: Nested Resources in REST/HTTP API URLs?
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/
- Ask HN: What's is your go to toolset for simple front end development?
- Recommendation reading (books/blogs) for best practices while designing REST APIs
-
Composing and nesting with JsonApiDotNetCore
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.
-
Relationships
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.
What are some alternatives?
ent - An entity framework for Go
ServiceStack - Thoughtfully architected, obscenely fast, thoroughly enjoyable web services for all
trustfall - A query engine for any combination of data sources. Query your files and APIs as if they were databases!
FFImageLoading - Fast & Furious Image Loading - Image loading, caching & transforming library for Xamarin and Windows
genql - Type safe TypeScript client for any GraphQL API
NancyFx - Lightweight, low-ceremony, framework for building HTTP based services on .Net and Mono. Note: This project is no longer maintained and has been archived.
graphql-directive-rest - GraphQL directive for easy integration with REST API
GraphQL for .NET - GraphQL for .NET
Sqlmancer - Conjure SQL from GraphQL queries 🧙🔮✨
Hot Chocolate - Welcome to the home of the Hot Chocolate GraphQL server for .NET, the Strawberry Shake GraphQL client for .NET and Banana Cake Pop the awesome Monaco based GraphQL IDE.
objection-filter - Filter objection.js models over HTTP using complex search queries
Breeze - Breeze for C#, F#, and VB.NET client applications