graphql-go-tools
pulldown-cmark
graphql-go-tools | pulldown-cmark | |
---|---|---|
27 | 8 | |
638 | 1,930 | |
2.0% | 2.0% | |
9.6 | 9.0 | |
1 day ago | 13 days ago | |
Go | Rust | |
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.
graphql-go-tools
-
Scaling GraphQL Subscriptions in Go with Epoll and Event Driven Architecture
If you're interested in the full implementation of the resolver, you can find it on GitHub.
-
Optimizing Go string operations with practical examples
https://github.com/wundergraph/graphql-go-tools/blob/dcd50bd...
Each iteration of this benchmark measures the aggregate performance of
- 1x ParseObject
- 3x AppendObject
- 3x MergeNodesWithPath
- 1x PrintNode
- 1x bytes.Equal comparison of two byte slices
The benchmark isn't actually benchmarking MergeNodesWithPath, it's benchmarking a much larger composite operation, which includes (multiple) calls to MergeNodesWithPath but also all of the above listed calls as well. If you want to measure MergeNodesWithPath, you would need to have each iteration of the loop do a single MergeNodesWithPath call, on the same JSON method receiver, and with the same input parameters.
-
Introducing astjson: Transform and Merge JSON Objects with Unmatched Speed in Go
You can check out the full code including tests and benchmarks on GitHub. It's part of graphql-go-tools, the GraphQL Router / API Gateway framework we've been working on for the last couple of years. It's the "Engine" that powers the Cosmo Router.
- GraphQL Router / API Gateway Framework Written in Golang
-
Building a high performance JSON parser
I've taken a very similar approach and built a GraphQL tokenizer and parser (amongst many other things) that's also zero memory allocations and quite fast. In case you'd like to check out the code: https://github.com/wundergraph/graphql-go-tools
-
A Blazingly Fast Open-Source Federation V1/V2 Gateway
The Cosmo Router is powered by graphql-go-tools, a highly mature and optimized GraphQL engine (MIT License) that is the fastest and most reliable implementation for Federation V1. The Cosmo Router builds on it with its own optimizations.
-
Cosmo Router: High Performance Federation v1 & v2 Router / Gateway
Cosmo Router is built on top of graphql-go-tools, a high performance GraphQL engine written in Go.
-
WunderGraph Cosmo: a open source alternative to Apollo Federation, GraphOS, Studio, etc...
For more than five years, we've been involved in the GraphQL ecosystem, building tools and services around GraphQL, like [graphql-go-tools (https://github.com/wundergraph/graphql-go-tools), a library to build GraphQL Gateways in Go.
-
Introducing Open Federation - a MIT-Licensed specification to build federated GraphQL APIs
I've been working on this library for more than 5 years now and it has been a great success. Almost 3 years ago, I started adding support for Apollo Federation to graphql-go-tools. As excited as I was about the idea of Federation, the community was not ready for it yet. I've added support for Subscriptions years ago, but demand for it was very low, so my focus shifted to solving other problems.
-
I want to contribute to open-source software written in Go
Check us out: https://github.com/wundergraph/graphql-go-tools
pulldown-cmark
-
CryptoFlow: Building a secure and scalable system with Axum and SvelteKit - Part 3
As a platform that allows expressiveness, we want our users to be bold enough to ask and answer questions with either plain text or some markdowns. Compiling markdown to HTML in Rust can be done via the pulldown-cmark crate. We used it in this utility function:
-
Building a high performance JSON parser
I also really like this paradigm. It’s just that in old crusty null-terminated C style this is really awkward because the input data must be copied or modified. But it’s not an issue when using slices (length and pointer). Unfortunately most of the C standard library and many operating system APIs expect that.
I’ve seen this referred to as a pull parser in a Rust library? (https://github.com/raphlinus/pulldown-cmark)
- Let Rust detect changes in the Markdown file and generate HTML.
-
Show HN: A Graphviz Implementation in Rust
Really glad to see this! Really want an easy way to render graphs in Rust without resorting to the graphiz binary.
What is the current status? Not seeing it listed anywhere, like if there are features that are not supported or if it uses certain layout algorithms but others are desired.
Would you be willing to make a `[lib]` available? I see you have a `lib.rs` but it'd be great if using it didn't require pulling in `[[bin]]` dependencies (you can mark them as optional and mark `required-features` on your bin like pulldown-cmark does [0] or split it into a separate crate in a workspace). It'd also be good to find an available name for the lib and get it published (looks like someone might be squatting on `layout`).
[0] https://github.com/raphlinus/pulldown-cmark/blob/master/Carg...
-
Using Rust with Elixir for code reuse and performance
Author here. I actually was not aware of cmark.ex - thanks for pointing it out.
In this case the code reuse was more important than pure native speed. We already had a Rust library that used pulldown-cmark [1] with some custom tweaks that we wanted to duplicate. Maybe this behavior could have been copied using cmark.ex too (we thought about doing this in pure Elixir, as mentioned in the post), but given how straightforward Rustler made integrating our existing code, this seems like the better choice.
[1] https://github.com/raphlinus/pulldown-cmark
It turned out that making the most popular Elixir Markdown processor, Earmark (originally written by Dave Thomas) and pulldown-cmark, a Rust Markdown processor, produce the same output was going to be difficult. We also required some customization that was not available in both libraries.
-
What are some examples of particularly well written crates?
The crate that's closest to production quality code is pulldown-cmark, but I don't hold it up as an example of well-written code, because it's not particularly easy to understand and there's a lot of very low level code to consume the CommonMark syntax - that helps with code bloat and compile time, but not clarity.
-
What are the Markdown features/extensions enabled in mdbook?
The Markdown processor is pulldown-cmark, which supports these extensions:
What are some alternatives?
bramble - A federated GraphQL API gateway
mdBook - Create book from markdown files. Like Gitbook but implemented in Rust
schema-stitching-handbook - Guided examples exploring GraphQL Tools v6+ Schema Stitching
nimler - Erlang/Elixir NIFs in Nim
gateway - A federated api gateway for graphql services. https://gateway.nautilus.dev/
doctave - A batteries-included developer documentation site generator
wundergraph - WunderGraph is a Backend for Frontend Framework to optimize frontend, fullstack and backend developer workflows through API Composition.
cmark - CommonMark parsing and rendering library and program in C
gqlparser - A port of the parser from graphql-js into golang
rust - Empowering everyone to build reliable and efficient software.
participle - A parser library for Go
cmark - 💧 Elixir NIF for cmark (C), a parser library following the CommonMark spec, a compatible implementation of Markdown.