Explore >> Select a destination
|
You are here 
|
yos.io | ||
| | | | |
electric-sql.com
|
|
| | | | | Web development has been progressing through an evolution of state transfer. Hybrid local-first architecture is the natural endgame for this progression. | |
| | | | |
blog.appsignal.com
|
|
| | | | | Learn how to create and use an Elixir gRPC server | |
| | | | |
blog.hao.dev
|
|
| | | | | Building a GraphQL API requires a deep understanding of the technology and best practices. It offers developers a high level of control and freedom, which is why it is so easy to get started. However, it is also why people can design themselves into a corner if they are not careful. Security and performance implications are just typical issues of software development. GraphQL also requires that the schema is well-designed and easy to maintain; otherwise, the development team will run into a world of pain. Additionally, the development team must be trained and skilled in using GraphQL, as it requires a different way of thinking about data and APIs. In this article, let's discuss when it is a good choice to adopt GraphQL and who it is for. | |
| | | | |
markus.oberlehner.net
|
|
| | | Learn how to use partial hydration with Eleventy and Preact and how to apply the principles of progressive enhancement to build resilient websites. | ||
