GraphQL Nested Queries | MACH Compliance | APIs

Speaker 0: Hello, everyone. Welcome to another episode of From the Field q and a with p and j. My name is Pedro,

Speaker 1: And I am John. Let's dive into some questions that we've had this past week. I will start off because I want to. So first question is, is there a feedback mechanism for content?

Speaker 0: So yeah. Yes. You are able to add comments and even at tag users on specific records as you can see in this video. Cool. Mhmm.

Mhmm. Next question. User, I'm not gonna try to pronounce that, on GitHub asks, is it possible to query data from multiple databases? Oh, this is a good one. And we hear this a lot, actually.

So

Speaker 1: Yeah. So it was it was answered by Wrike, but we do get this question a lot. By the way, Wrike is always watching. So if you ever ask a question in GitHub or Discord, he's probably already on top of it. But the answer is

Speaker 0: CTO and cofounder. True. If you don't know.

Speaker 1: Also guitar player, extraordinary. So he does everything. This is true. But yeah. So currently, the way that Directus is set up, it does connect to a single database.

That is the way that it is currently done, but stay tuned. So a little teaser there for you. Alright, Pedro. I think we have a I think we have a list of a few questions that might have some simple answers. So let's kinda hit a couple of them real quickly.

Okay. Great. So the the first question is, do you support GraphQL nested queries?

Speaker 0: Yeah. Yes. We do. Alright. Up on that one.

Speaker 1: Does your platform allow for reading, query, and content via API?

Speaker 0: Yes. Let's start the yes counter. That's 2 yeses.

Speaker 1: Does your platform allow for writing mutating content via API? Oh, do we

Speaker 0: have a 3? Do we have a 3? Yes. We have 3 yeses. That is a yes for that one.

Speaker 1: And since we're on the API train, are your APIs and platform mock compliant? So microservices, API first, composable, and headless.

Speaker 0: Yep. That is that is the ding ding ding. You have a winner. All yes. Yes on there.

Speaker 1: Kinda kinda convenient how all of those were yeses. I wonder how that was set up.

Speaker 0: I wonder.

Speaker 1: It's how we do it.

Speaker 0: So next question, and this is our final question, I think. So what percentage of the functionality of your platform or of the app is available through the APIs? Is there any functionality only available through the UI that is not available for from, UI that is not available for from, the API? And this is a question we get all the time and one of my favorites, but I'll let you answer it,

Speaker 1: John. Yeah. I just like answering it because I'd rather have Jonathan, our sales engineer, come on and answer it. He gets very excited when he's talking about this. Yeah.

Whenever you're interacting with the app, the inter the data studio itself, all of that is driven by the API. So every single click, every data change, everything that you do in Directus is done via API. So Mhmm. It's very exciting. He he gets very giddy when he's telling that.

But, yeah, everything that you can do in direct us is a 100% API compatible. So you can use those things, you know, some aggregate, whatever you wanna do via the APIs externally as well. So we are 100% API friendly.

Speaker 0: Yeah. And if you think about the architecture behind directus and what it is, it's like you have your your database, Directus installed on top, and then on top of that, there's the no code app. So Directus being the API, so it's database, APIs, app built on top of those APIs. Very cool.

Speaker 1: It's like a API sandwich, kinda.

Speaker 0: A API sandwich. Yeah. I like that. Sure. Alrighty.

Thanks for watching. We hope you're keeping warm. Please like and subscribe to this YouTube channel and to this, phenomenal q and a with p and j that we do, and feel free to hop into one of our communities, GitHub, Discord. We live inside of Discord as a company, So if you wanna come chat with John or myself, we are there probably 247 because we do not sleep. Yeah.

So always there to help answer your questions, and, we hope you contribute to the community. And until next time, good night. Good good night. Good good

Speaker 1: to good night. Good day, sir.

Speaker 0: I do. Yeah. Good night. Good morning. Good evening.

Good night wherever you are. Until next time. Goodbye. Bye