Designing the relationships between resources in your RESTful API

Defining your relations: embed your fields based on query parameters

{
id: "123456",
subject: "Message 1",
message: "This is my first message",
author: ?
}

Option 1: only ID

Option 2: full resource representation

Option 3: embedded fields based on query parameters

--

--

--

Développeur web et passionné de finances personnelles

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Everyone Should Know These 8 Python Functions

DevNet Create: Where Apps meet the Boogeyman — Face Your Fears!

How to pass CKS — Kubernetes Security Specialist exam. Part 2

Setting Expectations: The Life of Pablo

Kanye West’s Saint Pablo Tour in Toronto.

Apache Kudu series: 2. Troubleshooting for TABLET_DATA_TOMBSTONED

Proactive handling of distribution of item using IVR.

Kafka Streams Gotchas

What happens when you compile a C source code?

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Guillaume Viguier-Just

Guillaume Viguier-Just

Développeur web et passionné de finances personnelles

More from Medium

How to use GraphQL Directives efficiently?

GraphQL Directives

Application Framework — SE3040

Builder Design Patterns

Experience During Application Framework Group Project