Summary
In this chapter, we were introduced to the first design pattern called pipes. This pattern is not only useful for logically dividing related types but also has many other applications.
We started with pipes that logically divide our schema, using knowledge from DDD and applying it to create a GraphQL schema. Then, we moved on to pipes that restrict access to individual query and mutation sets, allowing only authorized users to access them. Expanding upon that, we looked at ownership pipes, which connect objects and establish ownership of objects from one set to another.
In the next chapter, we will start coding and learn how to transform an existing REST API into a GraphQL one.
