I’ve prepared a simple GraphQL API that returns the current time. Let’s start with learning how to do data fetching inside server components. Focusing on data engineering platforms development on cloud architectures. Well versed with micro-services and cloud agnostic application development. Agile and XP practitioner with a focus on continuous integration. In this blog post we’ll learn how to use Apollo Client in server components, how Next.js cache works and when you should use Apollo Client in server components and when to use them in Client Components. Application developer/Data Engineer with a vast experience of developing software products and platforms. That brings us a question, can you use Apollo Client with React Server Components? The answer is yes, but there’s nuances to that, especially when using Next.js 13! Feel free to skip over to the TLDR of this post if you want a summary on how to use Apollo with Next.js! networkTransport ( WebSocketNetworkTransport ( serverUrl baseUrl ) ).build () The base url uses ws as a protocol: ws://. To put it simply Server components allow you to run data fetching on the server removing the need of client side fetches in most cases! and I create the Apollo client by calling: ApolloClient.Builder ().

The most interesting feature is the introduction of React Server Components. Next.js 13 was probably one of the most awaited releases of Next.js It brought us the app directory, with support for layouts, React Server Components and more!

Apollo kotlin