By: Roy Derks In the evolving world of AI and language models, ensuring that outputs are factually accurate and relevant is crucial. Developers often rely on foundational models to generate responses based on company data, but large language models (LLM) can sometimes combine multiple pieces of information incorrectly, resulting in hallucination responses that are either inaccurate or entirely fabricated.
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Roy Derks
Why GraphQL Needs an Open Federation Approach
Looking at the current API landscape, it’s evident that enterprise GraphQL adoption has grown from a niche technology for frontend developers to a key technology for helping architects and backend developers combine APIs and other services. Gartner predicted this momentum in 2021, reporting that only 10% of enterprises were then using GraphQL in production, but it expected more than 50% of enterprises to adopt it by 2025.
Seven Key Insights On GraphQL Trends
GraphQL has emerged as a key technology in the API space, with a growing number of organizations adopting this new API structure into their ecosystems. GraphQL is often seen as an alternative to REST APIs, which have been around for a long time. Compared to Interfejsy API usług REST (or other traditional API specifications), GraphQL provides more flexibility to API consumers (like app developers) and delivers many benefits, along with a few new challenges to API development and delivery.
Seven Key Insights On GraphQL Trends
GraphQL has emerged as a key technology in the API space, with a growing number of organizations adopting this new API structure into their ecosystems. GraphQL is often seen as an alternative to REST APIs, which have been around for a long time. Compared to REST APIer (or other traditional API specifications), GraphQL provides more flexibility to API consumers (like app developers) and delivers many benefits, along with a few new challenges to API development and delivery.
Seven Key Insights On GraphQL Trends
GraphQL has emerged as a key technology in the API space, with a growing number of organizations adopting this new API structure into their ecosystems. GraphQL is often seen as an alternative to REST APIs, which have been around for a long time. Compared to API REST (or other traditional API specifications), GraphQL provides more flexibility to API consumers (like app developers) and delivers many benefits, along with a few new challenges to API development and delivery.
Seven Key Insights On GraphQL Trends
GraphQL has emerged as a key technology in the API space, with a growing number of organizations adopting this new API structure into their ecosystems. GraphQL is often seen as an alternative to REST APIs, which have been around for a long time. Compared to APIs REST (or other traditional API specifications), GraphQL provides more flexibility to API consumers (like app developers) and delivers many benefits, along with a few new challenges to API development and delivery.
Seven Key Insights On GraphQL Trends
GraphQL has emerged as a key technology in the API space, with a growing number of organizations adopting this new API structure into their ecosystems. GraphQL is often seen as an alternative to REST APIs, which have been around for a long time. Compared to REST-sovellusliittymät (or other traditional API specifications), GraphQL provides more flexibility to API consumers (like app developers) and delivers many benefits, along with a few new challenges to API development and delivery.
Seven Key Insights On GraphQL Trends
GraphQL has emerged as a key technology in the API space, with a growing number of organizations adopting this new API structure into their ecosystems. GraphQL is often seen as an alternative to REST APIs, which have been around for a long time. Compared to REST-APIs (or other traditional API specifications), GraphQL provides more flexibility to API consumers (like app developers) and delivers many benefits, along with a few new challenges to API development and delivery.
GraphQL Can Compose Headless Systems to Boost User Experience
With the rise of APIs, businesses can streamline their operations and automate workflows like never before. Two API technologies that have been gaining a lot of attention are headless (API-first) and GraphQL. Today’s Software Is Headless Headless services have become increasingly popular, especially in web development. A “headless” or “API first” service separates the frontend and backend applications, and offers an API instead of a web interface.
Roy Derks
Cookie Policy When you visit, the website may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device, but does not usually directly identify you. The information is mostly used to make the website display the embedded content you expect to see and work the way you expect it to. These cookies are necessary for the website to function and cannot be switched off in our systems.
React: Everything You Need to Know in 5 Minutes
Can you learn React in five minutes? Well, it depends on what you mean by “learn React”. In this blog post, you will “learn the basics of React” in five minutes by going over a few of the core concepts of React. Click here to watch the YouTube video version of this blog post. What Is React? React is a JavaScript library that is widely used for building user interfaces, particularly for single-page applications.
Can you compare GraphQL and tRPC?
There have been many discussions on Twitter around "GraphQL versus tRPC" for building a modern backend for your application. GraphQL has become popular in recent years as the defacto successor to REST, while tRPC solves the problem of end-to-end safety in fullstack applications. It's like comparing apples to oranges. TLDR; GraphQL is a query language, and tRPC is a library.
Hiding Your API Credentials Client Side Using a Proxy Server in React
Typically I advise people to use a server-side request to query a GraphQL API. This is because you can hide your API key in the server-side code. However, most Jamstack applications require you to write client-side code, so you can't use a server-side request. When you're in this situation, you can set up a proxy server to reroute your API requests internally, hiding the request from the user. In this post, I'll show you how to hide your API key using a proxy server in React.
GraphQL as the New API Gateway?
GraphQL has proven itself as the technology positioned to change the way we build modern APIs. Various companies have been using GraphQL to transform the way they interact with their APIs. Rarely is the composability it adds to your API architecture discussed, as GraphQL doesn’t only give you increased flexibility and performance gains. You can also use it to manage your APIs, for example, by implementing it as an API gateway.
2022 Noonies Programming Nominee Roy Derks on GraphQL, React, and More
Howdy Hackers! I’m Roy Derks! A tech speaker, writer, and software developer from the Netherlands! I’ve been nominated for the categories below, and if you've enjoyed anything I've written this year, please take some time to vote for me. What's your current role and what do you like about it? I’m focused on creating content and products for developers, especially around GraphQL.
Setup a GraphQL API for a Firebase Realtime Database With StepZen
The Firebase Realtime Database is a NoSQL database hosted in the cloud. Data is synchronized in real-time with every client on all platforms (Web, iOS, and Android). The data is stored as JSON and is shared by all of your customers when you create cross-platform apps. This ensures that all of your clients always have the most recent data available, even when offline. Firebase is a cloud-based platform from Google that allows you to build web and mobile applications quickly.
Untangling Enterprise API Architecture with GraphQL
For enterprises with many microservices or legacy services, the API architecture can become tangled and hard to manage. GraphQL can help untangle this mess by providing clients with a single endpoint where they can get all their data and interact with it uniformly. In this article, we’ll explore how GraphQL fits into enterprise API architectures and describe how to use GraphQL with your existing services.
Query data from HarperDB with GraphQL using StepZen
One of the most complex decisions when choosing a database is how the data is stored for you. But the days where you had to choose between a SQL- and NoSQL-based database are over. With HarperDB, you’ll get the best of both types of databases, as you can interact with the database via SQL and NoSQL through their REST API. They don’t support GraphQL out of the box, but you can use StepZen to get a GraphQL API that interacts with the REST API that HarperDB exposes.
Why GraphQL for Microservices?
In 2022, many companies have adopted microservices into their software architecture. By splitting up their services into smaller parts, these companies benefit from modularity, scalability and distributed development. But how these microservices communicate with each other or the outside world is often a point of discussion and a challenge. Popular patterns include API gateways or a data mesh to combine microservices.
Why GraphQL for Microservices?
In 2022, many companies have adopted microservices into their software architecture. By splitting up their services into smaller parts, these companies benefit from modularity, scalability and distributed development. But how these microservices communicate with each other or the outside world is often a point of discussion and a challenge. Popular patterns include API gateways or a data mesh to combine microservices.
Building A Data Layer for Microservices With GraphQL And StepZen
GraphQL is the perfect technology to bring your microservices together. You can use GraphQL as a data layer for these microservices and combine the data from all these services into a single, unified API. But building this data layer can be very time-consuming, as you need to connect the microservices into one schema. In this post, you'll learn step-by-step how to use StepZen to build this data layer in a declarative way using GraphQL directives.
Schema Stitching & Federation: Not the Best Solutions for GraphQL Microservices
Let's start by saying that Apollo did a fantastic job in bringing GraphQL where it is today. Libraries like Apollo Client and Apollo Server get a couple of million downloads per week. They also created schema stitching, which is now maintained in the open-source community, to bring together (micro)services that support GraphQL. Later they released Federation as a more complete solution. But this tool has one obvious design mistake.
Documenting GraphQL APIs
The main goal of API documentation is to help developers understand how to use an API. Suppose you’ve just released a new API and created the documentation that other developers can use to understand how your API works. This documentation can usually be generated automatically if you’ve followed an API specification such as OpenAPI. An excellent way to write documentation is to create static documentation with interactive code examples, which will help people get started.
React.js Projects
When you visit any website, it may store or retrieve information on your browser,usually in the form of cookies. This information does not usually identify you, but it does help companies to learn how their users are interacting with the site. We respect your right to privacy, so you can choose not to accept some of these cookies. Choose from the different category headers to find out more and change your default settings.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Roy
Contact Roy, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack