Exograph

We are excited to announce that Exograph can now run as a Cloudflare Worker! This new capability allows deploying Exograph servers at the edge, closer to your users, and with lower latency. This combination merges Cloudflare Workers' strength (automatically scaling, excellent start time, optimal placement) with Exograph's (simple way to create fast, secure backends, efficient execution, and excellent tooling). The result: cost-effective development and deployment. https://lnkd.in/ddejj-Vh

I have been thinking about "Why, after 6 years, I'm over GraphQL" (https://lnkd.in/g_XDCvbQ). I faced many of the same issues with my GraphQL implementations but came to a different conclusion that led to Exograph (https://exograph.dev/). ? Problem: GraphQL authorization is a nightmare to implement. ? Solution: A declarative way to define entity or field-level authorization rules. In Exograph, you define authorization rules alongside your data definitions. This not only makes it easy to audit authz rules, but lets you lean on the engine to enforce them. ? Problem: GraphQL queries can ask for multiple resources in a single query, overwhelming the backend. ? Solution: Trusted documents, query depth limiting, and rate limiting. Exograph supports trusted documents/persisted queries and other mechanisms to control the load on your backend. ? Problem: GraphQL queries can overwhelm the parser. ? Solution: The same solution as above. You can control the load on your parser by using trusted documents and limiting query depth. ? Problem: GraphQL queries can lead to the N+1 problem. ? Solution: Defer data fetching to a query planner. The classic and dreaded N+1! Exograph uses a query planner to ensure that you never run into this. ? Problem: Balancing authorization and the N+1 problem can be tricky. ? Solution: Make authorization rules a part of the query planning process. By making authorization rules a part of the query planning process, Exograph ensures that you never fetch data the user is not authorized to see. ? Problem: GraphQL makes it quite hard to keep code modular. ? Solution: Reduce the amount of code by leaning on a declarative approach. More code, more problems! In Exograph, you write only a few hundred lines of code to define even complex data models. ? Problem: GraphQL makes balancing authorization, performance, and modularity tricky. ? Solution: Simplify implementing GraphQL through a declarative way to define data models and authorization rules. This is the core of Exograph: declarative data models and authorization rules. Read the full blog post at https://lnkd.in/gBwpXMHF

Super excited to announce #pgvector support in Exograph! Exograph can now serve as a backend for #AI apps, where you put access control where it belongs: the data model. With access control in place, #RAG apps can retrieve only allowed data, thus eliminating a source of privacy issues. This feature supports: - Storing vectors for?unstructured data directly in your Postgres database - Retrieving documents based on vector distances - Schema creation and migration? - Setting up indexes and distance functions Here is the blog that goes into more detail: https://lnkd.in/gkZ2F_iH

We have just released Exograph 0.7, which brings with it a feature critical for production deployments of the GraphQL server: support for trusted documents! What are trusted documents, you ask? Also known as "persisted documents" or "persisted queries," these documents enhance Exograph's security by allowing only specific queries and mutations, thereby reducing the API surface and improving performance by shrinking payload size. Trusted documents streamline your development process by providing a pre-arranged way for clients to convey executable documents they'll be using, ensuring the server only executes those specified documents. This enhances security, optimizes bandwidth, and provides a focal point for testing. Curious about trusted documents, why they're essential, and how to use them in Exograph? Check out our latest blog post: https://lnkd.in/dfqvTjEK, which offers a conceptual overview, workflow guidance, and examples of organizing trusted documents for different clients. Ready to try it out? Head over to our GitHub repository to explore the updated todo application, now with trusted documents support: ?? Apollo Version: https://lnkd.in/dC-BpzfV ?? URQL: https://lnkd.in/diMM_dFt For detailed documentation and step-by-step instructions, visit our website: https://lnkd.in/dvBMekiS .Let's make GraphQL deployment in production safer with trusted documents! #Exograph #GraphQL #TrustedDocuments #Development #APISecurity

We are excited to announce the release of?Exograph 0.4! This release introduces several new features and enhancements, many in response to our users' feedback (thank you!). - NPM module support: Opens up the vast NPM module system to be easily used from Exograph. For example, you can now use the module for Stripe to check out a shopping cart, Slack to send messages, and Resend to send emails. - Railway integration: Deploy GraphQL server to Railway with ease. You can create and deploy the server from scratch in under three minutes. - The playground mode. Interact with a remote server without introspection support and still utilize all the GraphQL playground's goodies. - Access control improvements: Express even complex rules using higher-order functions. And much more. Learn more at https://lnkd.in/dJSD5cBE