Twitter | Search | |
Martijn Walraven
84
Tweets
229
Following
693
Followers
Tweets
Martijn Walraven Jul 27
Yeah, the plan is to extend the new multipart transport to improve batching, so results for individual queries in a batch can be streamed and delivered out of order.
Reply Retweet Like
Martijn Walraven Jul 17
We'll be writing more content about this, but we recommend data sources as a general pattern in Apollo Server 2. That gives you easy access to the context and a shared cache. For batching and deduplication, you can use DataLoader as part of the implementation.
Reply Retweet Like
Martijn Walraven Jul 17
Replying to @ajaxdavis
Up until now, all Apollo Server integrations share the same version number. So apollo-server-express 1.4 is using version 1.4 of Apollo Server. We'll be switching to independent versioning after the 2.0 release.
Reply Retweet Like
Martijn Walraven Jun 25
Replying to @Saeris @apollographql
Could you open an issue for this? You can definitely configure the config, that error should only occur if you put a dataSources key on the context yourself.
Reply Retweet Like
Martijn Walraven Jun 15
Yep, I’m here! Just walked out to grab some food.
Reply Retweet Like
Martijn Walraven Dec 4
I just realized I missed the CFP. Any chance you would accept a late submission for a talk on GraphQL and microservices, focusing on API composition and caching with GraphQL?
Reply Retweet Like
Martijn Walraven retweeted
Peggy Rayzis 👩🏼‍💻 Nov 1
Speakers are people, not props. 🙅 Here's why I withdrew from : RT for visibility please 🙏
Reply Retweet Like
Martijn Walraven retweeted
Apollo Oct 24
Today we're launching 🚀 Apollo Engine: the first-ever gateway!
Reply Retweet Like
Martijn Walraven Oct 24
Replying to @Anand_Walvekar
Yeah, I agree something like that makes sense. Please open an issue so we can keep track and discuss further!
Reply Retweet Like
Martijn Walraven Oct 22
Replying to @Saeris @apollographql
If you believe you've found a bug, could you open an issue (or PR!) for this on the repo?
Reply Retweet Like
Martijn Walraven 19 Oct 17
Replying to @nikgraf
Not sure if it helps, but you do run the proxy yourself, so auth doesn't really go through our service.
Reply Retweet Like
Martijn Walraven 19 Oct 17
Replying to @nikgraf
Not in the short term. Anything we could do to help with security concerns?
Reply Retweet Like
Martijn Walraven 19 Oct 17
Replying to @nikgraf
Reply Retweet Like
Martijn Walraven 19 Oct 17
Replying to @nikgraf
Supporting more envs like Lambda was a major reason for Apollo Tracing. You run Engine in front of Lambda, as a gateway.
Reply Retweet Like
Martijn Walraven retweeted
Apollo 3 Oct 17
The schedule is live! Awesome lineup covering everything from fundamentals to live queries:
Reply Retweet Like
Martijn Walraven retweeted
GraphQL Summit 16 Aug 17
⚡🐦 Tickets to Summit are here, along with our first 9 speakers! Get early bird discounts while they last:
Reply Retweet Like
Martijn Walraven 13 Aug 17
Good to hear! You should also be able to simplify ContentNode_content by extracting stuff into a common fragment.
Reply Retweet Like
Martijn Walraven 13 Aug 17
It works if you include the Content union type in fragmentMatcher.js:
Reply Retweet Like
Martijn Walraven 13 Aug 17
I'm probably missing something here, but shouldn't this work on both Apollo and Relay?
Reply Retweet Like
Martijn Walraven 13 Aug 17
Is your server available somewhere so I can try out the queries?
Reply Retweet Like