Introduction to Dgraph's Architecture

In traditional applications today, our database sits in layer 3. This is a problem because a large development effort must take place to build out the web service before front-end work can begin.

Dgraph has flipped this model around. By moving the database to layer 2 and generating API's based on schema, Dgraph has drastically simplified this development process and given us a big productivity gain.

Let's take a look at how they've done this.

----

Want to access our full online courses?

For everything else:

[jaysistar]

Scalability isn't a bonus; it's a requirement. Great video!

[AlienSpaces]

Would recommend taking a good look into how the business/model layer is implemented in dgraph before making a decision as to whether the dgraph solution is appropriate for your project.

[AndrewPrice]

Also look into Hasura, which allows other DBs to do what dgraph does here :)

[GustavoDiaz]

It reminds me to JAM stack and using Prisma js

[RedCloudServices]

I like Hasura but you’re forced to use SQL backends. Learning about dgraph but most of the architecture benefits you’re mentioning come from GraphQL spec not dgraph