adamkl

25 ms·

211.
by adamkl 9y ago
Exactly!
212.
by adamkl 9y ago
Everybody focuses on the “graph” aspect of GraphQL (obviously), but at its core, GraphQL let’s you define methods with input types and return types in the same fashion as you would with any other RPC framework. If you define your methods an
213.
by adamkl 9y ago
We were looking at an architecture exactly like this (GraphQL front end, backed by gRPC microservices), because we liked the strongly typed interfaces of gRPC, and the flexibility of GraphQL, but we ran into some technology issues (http&#x2
214.
Use graphql-weaver to combine multiple GraphQL servers into one API(github.com)
2 points by adamkl 9y ago|0 comments
215.
by adamkl 9y ago
Is the GraphQL spec itself under the BSD+patents clause? Or just their specific implementation? Couldn’t somebody like the Apollo crew create their own implementation if necessary?
216.
by adamkl 9y ago
Async/Await can definitely increase the complexity of the codebase and make stack traces difficult to interpret (especially if you aren't clear on what is happening under the hood), but if you work on any sort of web-based/di
217.
by adamkl 9y ago
I've recommended this book in the past, and I'll recommend it again. Functional Programming in Scala [1] does a good job of taking traditional stateful object oriented code and refactoring it using pure functional approaches. Comi
218.
by adamkl 10y ago
Take a look at Gary Bernhardt's talk "Boundaries"[1]. It touches on this very topic and was quite the eye-opener for me (having experienced all the same issues you've described). [1] https://www.destroyallsoftw
219.
by adamkl 10y ago
It nice to see documentation on a real world implementation of this architecture, and if anyone is interested in more detail, I'd suggest this book[1] on my to-read list (it details a very similar approach). I've done SOA, and n-t
220.
by adamkl 10y ago
I'm just starting to pick up Scala (and functional programming for that matter) and I've been working my way through Functional Programming in Scala[1]. So far, it does a good job of teaching functional programming by taking state
221.
Thirteen ways of looking at a turtle(fsharpforfunandprofit.com)
2 points by adamkl 10y ago|0 comments