/explore
|
You are here 
|
blog.owulveryck.info | ||
| | | | |
mfbmina.dev
|
|
| | | | | The first time I heard about RPC, I was in a distributed systems class while completing my bachelor's in computer science. I like it but didn't fully understand why I should use it instead of REST. Time passed, and I started working at a company where the legacy services use SOAP. I remember thinking: "hm, that's cool! It is like RPC but using XML instead! Years later, I heard for the first time about gRPC, but I've never fully understood it until now! | |
| | | | |
frederickvanbrabant.com
|
|
| | | | | Microservices can solve a lot of architectural problems, and sometimes create a few fun new ones. A big problem however is connecting these services to each other. Can GRPC lend a hand here? | |
| | | | |
mherman.org
|
|
| | | | | This tutorial looks at how to implement an API with Node, gRPC, and Postgres. | |
| | | | |
lexi-lambda.github.io
|
|
| | | [AI summary] This article is a comprehensive exploration of Haskell programming, covering its strengths, challenges, and the author's personal reflections on the language and its community. The piece delves into topics such as Haskell's type system, effect systems, and the use of libraries like lens and Text. It also addresses broader issues like the community's debates, the role of Haskell in modern software development, and the importance of type safety and abstraction in programming. The author reflects on their journey with Haskell, emphasizing the language's ability to challenge and inspire while acknowledging its imperfections. The conclusion highlights the significance of Haskell in the design space of programming languages and the author's commitment... | ||
