jensneuse

8 ms·

61.
by jensneuse 3y ago
This is really cool. We've just created a POC that bridges Federated GraphQL Subscriptions and NATS, so this could maybe work together? Here's a small video of combining Federated Subscriptions and event driven architecture throug
62.
Astjson: Merge JSON objects at the AST layer using Go(wundergraph.com)
2 points by jensneuse 3y ago|0 comments
63.
by jensneuse 3y ago
We're using similar techniques to parse and merge JSON objects, which could be applied to this problem as well. Essentially, you could index the whole input into an AST and the. Traverse the AST to find the data you're looking for
64.
by jensneuse 3y ago
When you build a startup, you have to go through so much crap, a lot of people wouldn't do that for money. But there's another aspect. Early on in the startup life, sales is not just about selling but "exploring". You ha
65.
by jensneuse 3y ago
I'm very strong in logical analysis and strategic thinking. My problem though is that I have a natural tendency to not talk to people. Ask me a question and I'm happy to answer, but I don't like to initiate conversations. Ste
66.
by jensneuse 3y ago
The inverse is also true. As a technical founder, and maybe even an introvert like me, you should definitely look for a non-technical co-founder who can help you with networking, etc... I found my dream co-founder through YC Co-founder matc
67.
Astjson: Transform and Merge JSON Objects with Unmatched Speed in Go(wundergraph.com)
1 points by jensneuse 3y ago|0 comments
68.
by jensneuse 3y ago
It's possible that my comment is misinterpreted. YouTube is a service provided by a company and you have to pay for it in some way. You can pay with your time and watch ads, you can pay money and not worry about ads, or you can somehow
69.
by jensneuse 3y ago
They should definitely offer a free or almost free student version. Supporting students is a good thing.
70.
by jensneuse 3y ago
Not a lot of people will like to hear this, but you can pay YouTube a few dollars per month to remove ads and allow the player to run in the background. A lot of tech people will probably earn that money in a few minutes. Is it really worth
71.
How to analyze the usage of your GraphQL Schema(wundergraph.com)
1 points by jensneuse 3y ago|0 comments
72.
GraphQL Router / API Gateway Framework Written in Golang(github.com)
1 points by jensneuse 3y ago|0 comments
73.
by jensneuse 3y ago
Have you seen this? https://www.apollographql.com/blog/announcement/backend/anno...
74.
by jensneuse 3y ago
It's a bit verbose.
75.
by jensneuse 3y ago
I build GraphQL API gateways / Routers for 5+ years now. It would be nice if trusted Documents or persisted operations were the default, but the reality is that a lot of people want to open up their GraphQL to the public. For that reas
76.
by jensneuse 3y ago
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.c
77.
by jensneuse 3y ago
Don't hire a single non founder before PMF. Don't build anything without real commitments from customers. Focus on distribution, go to market and product in this order.
78.
by jensneuse 3y ago
That's fantastic and I hope to see more of this.
79.
by jensneuse 3y ago
> Many organizations choose REST over GraphQL due to more established conventions, simplicity, and the ability to leverage standard HTTP features directly. I strongly disagree with this. REST APIs are usually a complete mess and follow n
80.
A new algorithm to solve the N+1 Problem(wundergraph.com)
3 points by jensneuse 3y ago|0 comments
81.
Show HN: Cosmo – OSS Alternative to Apollo Federation / GraphOS(github.com)
7 points by jensneuse 3y ago|0 comments
82.
by jensneuse 3y ago
We're soon launching a GraphQL Analytics, Tracing and Metrics stack on top of OTEL. We've built a custom OTEL exporter to Clickhouse in go, so we can export OTEL traces and Prometheus metrics all to Clickhouse. We've built th
83.
by jensneuse 3y ago
An alternative to what's suggested in this post, how about going API first or even API only? Don't build a frontend at all, just build an API. E.g. you can deploy things on fly.io just by using their GraphQL and REST APIs. The adv
84.
by jensneuse 3y ago
I didn't know Stefan well but had some conversations on LinkedIn. Really cool dude. He had a lot of influence in the API ecosystem with presentations on REST, Hypermedia and such. rip
85.
by jensneuse 3y ago
With tRPC and similar frameworks, you infer client types from server definitions without including actual server code into the client. As much as I like GraphQL, one thing that IDEs really suck at is recognizing when generated code changes.
86.
by jensneuse 3y ago
I'm a big fan of tRPC. It's amazing how it pushed TypeScript only stacks to the limit in terms of DX. Additionally, it made the GraphQL community aware of the limitations and tradeoffs of the Query language. At the same time, I th
87.
Show HN: Preview Comments using GitHub Discussions as storage(openpreviews.com)
2 points by jensneuse 3y ago|0 comments
88.
by jensneuse 3y ago
I've built something similar with a focus on returning structured data from the Agent and making it simple to expose an Agent as an OpenAPI. If that sounds interesting, I've wrote up some details here: https://wundergra
89.
Using invisible divs in GitHub Discussions as a key-value store(wundergraph.com)
2 points by jensneuse 3y ago|0 comments
90.
by jensneuse 3y ago
We've recently built an adapter for NATS KV so you can easily expose it through an HTTP-based GraphQL API. ( https://docs.wundergraph.com/docs/databases/kv ) We're also looking at supporting streams in the

More ›