Joschka Tillmanns - When Dgraph + GraphQL Becomes Boring

About Joschka

Hi, I’m Joschka, a Software Engineer and recent Co-founder of the startup Mooncamp based in Cologne! I previously worked for real.digital, a successful e-commerce company, where I was responsible for supporting the company’s growth by shifting the organization’s tech architecture to microservices. I’m fascinated by cloud technologies and complex engineering problems.

When Dgraph + GraphQL Becomes Boring

In this talk, Joschka will be diving into Mooncamp’s experience with Dgraph GraphQL and sharing best practices that improve its workflow.

Have questions for Joschka? Submit them below.

Joschka would love to answer them!

Haven’t signed up for the free conference yet?

Grab your free tickets here: https://graphqlcon.space

Follow Joschka

GitHub: https://github.com/jostillmanns

Twitter: https://twitter.com/jostillmanns

LinkedIn: https://www.linkedin.com/in/joschka-tillmanns-152976143/

1 Like

Hi Joschka:
Do you feel graphql and dgraph can simplify microservices development. IMO, I feel we often miss out on the role of graphql in managing bounded contexts and their interconnected-ness, and your insight will be valuable to us. Thanks!

Way new to Graph but your note had me scratching my brains.
Since you have mentioned boring, can I ask if you could share one scenario where you could have absolutely omitted working with Graph?

Thanks & looking forward to your note!

1 Like

Hi @JoeD1992

Do you mean, where I could have achieved better results without the use of GraphQL?, because I might have to disappoint you in this regard. Up until now we didn’t encounter any challenges where we wished for a different solution. (if you for instance consider document based or relational databases as a different solution).

1 Like

Thank You Joschka! I get your point.
So, would you say that GraphQL is the ultimate sword you have wielded till date?