---
title: "Comment by Patrick Werz on \"How to Avoid Composite IDs in GraphQL with DynamoDB (feat. AppSync)\" | Hashnode"
description: "Hi Benoit, thanks for sharing. This trick (splitting up the Id) would still be possible without denormalizing the data, right?"
url: "https://hashnode.com/posts/how-to-avoid-composite-ids-in-graphql-with-dynamodb-feat-appsync/61410610c5f31102b885d67f/comment/62b3852886d22092a754724c"
---

[Discussion](https://hashnode.com/posts/how-to-avoid-composite-ids-in-graphql-with-dynamodb-feat-appsync/61410610c5f31102b885d67f)

Comment [How to Avoid Composite IDs in GraphQL with DynamoDB (feat. AppSync)](https://hashnode.com/posts/how-to-avoid-composite-ids-in-graphql-with-dynamodb-feat-appsync/61410610c5f31102b885d67f)

[Patrick Werz](https://hashnode.com/@PatrickServerless)

[Jun 22, 2022](https://hashnode.com/posts/how-to-avoid-composite-ids-in-graphql-with-dynamodb-feat-appsync/61410610c5f31102b885d67f/comment/62b3852886d22092a754724c)

Hi Benoit, thanks for sharing. This trick (splitting up the Id) would still be possible without denormalizing the data, right?

[Benoît Bouré](https://hashnode.com/@bboure)

[Jun 23, 2022](https://hashnode.com/posts/how-to-avoid-composite-ids-in-graphql-with-dynamodb-feat-appsync/61410610c5f31102b885d67f/comment/62b3852886d22092a754724c#reply-62b4345c92447c9aed5b17ce)

Do you mean without denormalizing an `id` attribute? Yes, it would still work. But keep in mind that it would be easier to return from the API if it comes pre-denormalized.
