https://www.ory.sh/ logo
#talk-kratos
Title
# talk-kratos
r

rhythmic-toddler-31735

05/04/2022, 1:40 PM
Hello again, I'm here to ask your advice again 😛 I've figured setup for my app, now I'd like to know what's recommended way to get identity details. Right now im creating acc in my main app database after kratos creates account with id attached. My understanding is that duplicating too much data is not the best idea so it's better to not hold 'traits' that could change in main database (so i'm only storing id and email there rn). Now let's say i have 'comments' table with 'userId' and 'text'. When I'm loading one page of comments (let's say 20) am i supposed to make 20 GET Identity requests? I think there's no endpoint that takes array of id's to retrieve it right? Is that good approach or is it better to store 2 copies of traits - one in my main app db, one in kratos - and keep them in sync with web hooks?
👀 1
s

steep-lamp-91158

05/04/2022, 1:45 PM
you mean because the comments are written by various people and you need their name/... to display who is the author?
r

rhythmic-toddler-31735

05/04/2022, 1:45 PM
Exactly, in the future that could expand to users belonging to certain groups, which could affect how the user is displayed in the app. Moreover i'd like to understand what's the best way to work with ory so I won't make mistakes at 'design' stage :P
s

steep-lamp-91158

05/04/2022, 4:37 PM
we recommend to store the data needed for authentication, but not really more than those I agree that duplication should be avoided in this specific case it would actually be nice to have a bulk fetch API, you can open an issue so we can discuss there it would be possible to use e.g. a key-value store on your side to cache the identity information, and then fall back to kratos for getting the source-of-truth data
r

rhythmic-toddler-31735

05/04/2022, 5:11 PM
2 Views