Frequently Asked Questions

Product Information & Microservices Architecture

What is a content microservice, and how does Hygraph support building one?

A content microservice is a specialized microservice focused on content management tasks such as storage, transformation, and delivery. Hygraph enables you to create content microservices by leveraging its Content Federation and Remote Source features, allowing you to integrate content from multiple remote sources and provide a unified API for content delivery across applications. For example, you can connect external eCommerce data sources and fetch them alongside your Hygraph-managed content. Note: Setting up advanced integrations may require familiarity with GraphQL and API configuration. Source

How does Hygraph integrate with Remix for content microservices?

Hygraph integrates with Remix by exposing a high-performance GraphQL Content API endpoint, which you can query from your Remix application using Apollo Client or similar tools. The tutorial demonstrates configuring a Remix app to fetch both Hygraph and external data (e.g., from Platzi Fake Store) via unified GraphQL queries. The process involves updating your ApolloClient URI with the Hygraph API endpoint and mapping over the returned data to render content in your app. Note: Developers must handle authentication and error states as part of the integration. Source

What is Content Federation in Hygraph, and why is it useful?

Content Federation in Hygraph allows you to integrate multiple data sources (including remote GraphQL APIs) into a single unified API, eliminating the need for data duplication and enabling consistent content delivery across channels. This is especially useful for organizations managing content from various platforms or microservices. Note: Content Federation setup requires schema configuration and may not be suitable for teams unfamiliar with GraphQL schemas. Source

Features & Capabilities

What are the key features of Hygraph relevant to content microservices?

Key features include GraphQL-native architecture, Content Federation, Remote Source integration, high-performance API endpoints, and support for custom schema definitions using GraphQL SDL. These features enable developers to build modular, scalable content microservices and integrate external data sources efficiently. Note: Advanced features may require technical expertise in GraphQL and API management. Source

Does Hygraph support integration with external APIs and data sources?

Yes, Hygraph supports integration with external APIs and data sources through its Remote Source feature. You can connect to external GraphQL APIs, configure authentication headers, and define custom schema mappings to fetch and manage external data alongside your Hygraph content. Note: Only GraphQL-based remote sources are supported for federation; REST APIs require separate handling. Source

What technical documentation is available for developers building with Hygraph?

Hygraph provides extensive technical documentation, including API reference guides, schema component documentation, integration guides for platforms like Mux and Akeneo, and AI feature documentation. Developers can access these resources at https://hygraph.com/docs. Note: Some advanced guides assume prior experience with GraphQL and headless CMS concepts.

Implementation & Onboarding

How long does it take to implement Hygraph for a content microservice project?

Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph offers starter projects, structured onboarding, and community support to accelerate adoption. Note: Complex integrations or large-scale migrations may require additional time for schema design and data mapping. Source

What resources are available to help new users get started with Hygraph?

New users can access a free-forever account, starter project templates, structured onboarding (including introduction calls and technical kickoffs), comprehensive documentation, and community support via Slack. Training resources such as webinars and how-to videos are also available. Note: Some resources may require registration or joining the Hygraph community. Source

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for its hosting infrastructure, and GDPR compliant. These certifications ensure adherence to international standards for information security and data protection. Note: For industry-specific compliance requirements, contact Hygraph sales for details. Source

What security features are available in Hygraph?

Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin policies and IP firewalls). All endpoints use SSL certificates. Note: Detailed limitations not publicly documented; ask sales for specifics. Source

Performance & Scalability

How does Hygraph ensure high performance for content delivery?

Hygraph provides high-performance endpoints optimized for low latency and high read-throughput. A read-only cache endpoint delivers 3-5x latency improvement, and the platform actively measures GraphQL API performance. Developers can access performance insights in the GraphQL Report 2024. Note: Actual performance may vary based on integration complexity and network conditions. Source

Use Cases & Customer Success

Who can benefit from using Hygraph for content microservices?

Hygraph is suitable for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It is used in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Teams seeking to modernize content management, integrate multiple data sources, and deliver content across channels can benefit from Hygraph. Note: Teams without GraphQL experience may require additional onboarding. Source

Can you share examples of companies using Hygraph for content microservices?

Notable companies using Hygraph include Samsung (improved customer engagement by 15%), Komax (3x faster time to market), AutoWeb (20% increase in website monetization), Voi (scaled multilingual content across 12 countries), and Dr. Oetker (enhanced digital experience with MACH architecture). See more at Hygraph's case studies page. Note: Results may vary by use case and implementation.

Pain Points & Limitations

What common challenges does Hygraph address for content teams?

Hygraph addresses developer dependency for content updates, legacy tech stack modernization, content inconsistency across regions, workflow inefficiencies, high operational costs, slow speed-to-market, and integration difficulties with third-party systems. Note: Teams with highly specialized or legacy systems may require custom integration work. Source

What are the limitations of using Hygraph for content microservices?

Hygraph requires familiarity with GraphQL for advanced schema and API configuration. Only GraphQL-based remote sources are supported for federation; REST APIs need separate handling. Some advanced features may require technical expertise, and detailed limitations are not publicly documented—contact sales for specifics. Source

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Watch replay now

How to create content microservices with Hygraph and Remix

Learn how to leverage the Hygraph remote source feature to create content microservices instead of building one from the ground up.
Joel Olawanle

Last updated by Joel 

Jan 21, 2026

Originally written by Joel

How to create content microservices with Hygraph and Remix

Content microservices are a specialized form of microservices in software architecture that focus on content management tasks like storage, transformation, and delivery. They let you decouple content management from your application’s core logic, ensuring efficient content distribution across various platforms and channels.

This tutorial explores content microservices and how they work behind the scenes. You’ll also learn how to leverage the Hygraph remote source feature to create content microservices instead of building one from the ground up, as well as how to retrieve such content in a Remix application.

#Content microservice with Hygraph and Remix

Setting up a content management microservice from scratch is no small feat. Leveraging Hygraph can significantly streamline the process of creating content microservices using its Content Federation feature. It allows you to integrate content from multiple remote sources seamlessly, providing a unified API to fetch, manage, and deliver content across applications.

To try things out, we’ll create and configure a Hygraph application to retrieve external eCommerce data from the Platzi Fake Store GraphQL API alongside the data provided by Hygraph's commerce shop template. We’ll then render them in a Remix application.

#Content Federation with Hygraph

Let’s proceed with setting up our content microservice on the Hygraph platform. If you haven’t already, create a free-forever account, navigate to the new project page, and select the Commerce Shop template, as shown in the image below.

cloning a project in hygraph

Configure the project details as preferred and click the + Add p**roject button to continue. Next, navigate to the Schema builder on the left sidebar of your Hygraph dashboard, locate Remote Source**s, and then click the Add button next to it.

Fill in the details for the new remote source and set its type to GRAPHQL, as shown in the image below.

adding a remote source to hygraph

The data is also shown below for enhanced accessibility:

  • Display name: Fake Store API
  • Prefix is automatically generated
  • Base URL: https://fakeapi.platzi.com/

Hygraph provides additional options for users to pass headers, including API keys and other authentication parameters, ensuring secure communication with the remote source URL. Additionally, you can define the structure of your remote source data using GraphQL schema definition language (SDL), allowing for custom type definitions and tailoring the integration to your specific requirements.

Next, you’ll need to add a new data field for our remote source to fetch data alongside the regular models in Hygraph. Navigate to the Schema > Query tab and click the GraphQL section, as shown below.

adding a graphql query field to hygraph

Next, set the display name for this new data field and ensure the remote source is the same as you created earlier. Additionally, under the Query field, select Product since we’re trying to set up a query to access the products from the Platzi API. The API ID is generated automatically, and you can set the other configuration options to your taste.

configuring the graphql remote source

To proceed, click the Add button, and we’re done integrating our basic content microservice! You can already navigate to the Hygraph API playground and start interacting with the data from our remote source, as shown in the image below.

querying remote data from api playground

Finally, you must retrieve the content API endpoint to fetch this data remotely from any application. Navigate to your Project Settings > API Access and copy the High**-**Performance Content API URL shown in the image below.

enabling hygraph-s content api

Keep this URL in a safe space for now; in the next section, we will dive into fetching data in our Remix application.

#Fetching Hygraph content in Remix

Let’s create a new Remix application with the remix-apollo template by running the following command:

npx create-remix@latest --template jgarrow/remix-apollo

This template is a basic setup for an apollo-graphql and Remix project and already includes all the necessary setup you need to get GraphQL working.

Running this command will ask if you want to initialize a new Git repository for your project, as well as if you want to install dependencies with npm. Select the Git option as preferred, and choose “yes” for the second option to continue.

installing remix

Now, you’ll need to update your GraphQL API endpoint. Open app/entry.client.tsx and update the ApolloClient URI with the High Performace Content API you copied from your Hygraph dashboard earlier.

Open the app/entry.server.tsx and apply the exact change; everything should be smooth from here on.

Let’s try fetching our Hygraph and Platzi Fake Store products in our Remix app. Open the default app/route/index.tsx file and replace its content with the code below.

import { gql, useQuery } from "@apollo/client";
const PRODUCTS_AND_FAKESTORE_QUERY = gql`
query {
products {
id
name
price
description
images {
url
}
}
fakeStore {
id
title
price
description
images
}
}
`;
export default function Index() {
const { loading, error, data } = useQuery(PRODUCTS_AND_FAKESTORE_QUERY);
if (loading) return <p>Loading...</p>;
if (error) return <p>Error: {error.message}</p>;
return (
<div className="container">
<div>
<h2>Products</h2>
<div className="row">
{data.products.map((product) => (
<div className="col-md-3 mb-4" key={product.id}>
<div className="card" style={{ width: "18rem" }}>
<img
src={product.images[0].url}
className="card-img-top"
alt="..."
/>
<div className="card-body">
<h5 className="card-title">{product.name}</h5>
<p className="card-text">{product.description}</p>
<p>${product.price}</p>
</div>
</div>
</div>
))}
</div>
</div>
<hr />
<div>
<h2>Fake Store Products</h2>
<div className="row">
{data.fakeStore.map((fakeProduct) => (
<div className="col-md-3 mb-4" key={fakeProduct.id}>
<div className="card" style={{ width: "18rem" }}>
<img
src={fakeProduct.images[0]}
className="card-img-top"
alt="..."
/>
<div className="card-body">
<h5 className="card-title">{fakeProduct.name}</h5>
<p className="card-text">{fakeProduct.description}</p>
<p>${fakeProduct.price}</p>
</div>
</div>
</div>
))}
</div>
</div>
</div>
);
}

In the code above, a new GraphQL query named PRODUCTS_AND_FAKESTORE_QUERY is defined that fetches data from products and fakeStore. Loading and error states are also handled to provide feedback to the user while data is being fetched.

If the data is successfully fetched, then two sections are rendered: one for products and another for fakeStore data. Finally, map over the data arrays for each source and render individual product items, displaying their respective properties such as name, price, description, and images.

To start a local development environment and test the project, run the following command:

npm run dev

Visit the URL provided in your console, and you should see all the products configured in our Hygraph application in the browser.

shop displaying products

You can access the complete code in this GitHub repository.

#Conclusion

In this article, we've explored the concept of content microservices, demonstrating how Hygraph and Remix can be used to create them.

Sign up today to unlock the full potential of content microservices with Hygraph's flexible, powerful platform — and the best part? It's free forever. You can also join our Slack community to stay abreast of the latest updates and engage with fellow developers.

Blog Author

Joel Olawanle

Joel Olawanle

Joel Olawanle is a Frontend Engineer and Technical writer based in Nigeria who is interested in making the web accessible to everyone by always looking for ways to give back to the tech community. He has a love for community building and open source.

Share with others

Sign up for our newsletter!

Be the first to know about releases and industry news and insights.