Hasura stands out as a formidable player in the realm of modern web development. Particularly for those projects that demand efficient, flexible, and scalable data management solutions. Its prowess in automatically generating CRUD operations, coupled with its robust handling of relationships and support for complex queries via PL\/SQL functions, positions it as a highly productive tool for developers. <\/p>\n\n\n\n
This blog post, instead of talking about how to set it all up; will take a look at the good, the bad, and the nitty-gritty of using Hasura for projects.<\/p>\n\n\n\n
Have you ever wished talking to your database was as easy as ordering pizza? Welcome to Hasura. In the world of building apps, dealing with databases can feel like trying to solve a puzzle without all the pieces. <\/p>\n\n\n\n
That’s where Hasura comes in, acting not just as a simple translator but as a powerful connector that lets your app chat fluently with your database, especially if it’s PostgreSQL (though it’s open to connecting other databases too). Hasura uses foreign keys to track relationships between tables, enabling easy use of these relationships within GraphQL queries.<\/strong> For example, if there is a base_organization relationship, you can include this relationship within a nested query to retrieve related data.<\/p>\n\n\n\n Hasura offers several advantages, including its ability to connect to multiple sources, an integrated ORM with UI for simple migrations, support for basic SQL migrations, and automatic creation of CRUD operations that can be customized with GraphQL. It allows you to define tables, such as the user table, which triggers the creation of corresponding CRUD operations like Another benefit is that it has its official Docker image and can be hosted anywhere or in the Hasura Cloud which has other perks I won’t list here.<\/p>\n\n\n\n Finally, since it uses GraphQL, when using Typescript it is very easy to have typed requests since the generated schema will include all the types necessary, something that doesn’t happen with REST APIs.<\/p>\n\n\n\n I would say the biggest downside in my opinion is that since it uses GraphQL it\u2019s very easy to execute the GraphQL queries directly in the frontend that can expose the mutations\/queries to the client. It\u2019s designed like that and the documentation encourages that, but not all graphQL should be exposed. <\/p>\n\n\n\n I use it with Next.js and our team instead uses the custom server approach and creates a custom graphQL schema to call Hasura from Next.js backend instead of directly the frontend. This allows us to check permissions and remove the graphQL schema from the client.<\/p>\n\n\n\n I wanted to mention that it didn’t support NoSQL but the latest development has MongoDB on beta. <\/p>\n\n\n\n Finally, it\u2019s not as popular as other similar alternatives like Prisma.<\/p>\n\n\n\n What I like about Hasura is that it automatically creates all the possible CRUD operations and those can be customized with GraphQL. So I only have to define a table, for example I define the table user in a migration.<\/p>\n\n\n\n So now Hasura will track the table and will create an Hasura will use the foreign keys to other tables to create graphql relations and track them to use them easily in the custom mutations\/queries like this.<\/p>\n\n\n\n Let’s suppose there is a table organization and Hasura tracks it via the For more complex queries, Hasura supports writing plain PL\/SQL functions, allowing developers to write any necessary SQL without having to learn a new ORM syntax. This provides flexibility in handling project-specific requirements.<\/p>\n\n\n\n Here we add a computed property that can be exposed as a GraphQL property. <\/p>\n\n\n\n Inside these functions we can write any custom SQL needed for the project, for non computed properties a new table will be needed so Hasura can map the return type but there is no limit in what the SQL can have.<\/p>\n\n\n\n We can check roles and check that they can only query their own data, known as ACL (access list control). While some other frameworks are very good at this, Hasura needs a lot of configuration for this. Let\u2019s see an example:<\/p>\n\n\n\nThe pros and cons of Hasura.io <\/h2>\n\n\n\n
Pros<\/strong><\/h3>\n\n\n\n
insert_user, update_user, and delete_user.<\/code><\/strong> These operations can then be used in GraphQL queries and mutations, providing flexibility in defining your application’s logic.<\/p>\n\n\n\nCons<\/strong><\/h3>\n\n\n\n
Examples of using Hasura.io<\/h2>\n\n\n\n
CREATE TABLE public.\"user\" (\n\tid serial4 NOT NULL,\n\t\"name\" text NULL,\n\temail text NULL,\n\tusername text NULL,\n\t\"password\" text NULL,\n\tcreated_at timestamptz DEFAULT now() NOT NULL,\n\tupdated_at timestamptz DEFAULT now() NOT NULL,\n\tis_enabled bool DEFAULT true NOT NULL\n);<\/pre>\n\n\n\n
insert_user, update_user, delete_user<\/code><\/strong> and user GraphQL mutations\/queries that include the basic CRUD operations. To use them it\u2019s necessary to write customizations like these: <\/p>\n\n\n\nquery ExampleQuery {\n user(where: {is_enabled: {_eq: true}, password: {_is_null: false}}) {\n email\n id\n is_enabled\n last_login\n name\n }\n}<\/pre>\n\n\n\nHandling relations with Hasura<\/h3>\n\n\n\n
base_organization<\/code><\/strong> relationship. So this allows to use relationship inside the where statement and just by including the relationship in a nested query it adds it in the select.<\/p>\n\n\n\nquery MyQuery {\n user(where: {base_organization: {name: {_eq: \"devto\"}}}) {\n email\n id\n is_enabled\n last_login\n name\n base_organization {\n name\n }\n }\n}<\/pre>\n\n\n\nComplex queries in Hasura.io<\/h3>\n\n\n\n
CREATE OR REPLACE FUNCTION computed_full_name(user_row \"user\")\nRETURNS TEXT AS $$\nBEGIN\n IF user_row.first_name IS NOT NULL OR user_row.last_name IS NOT NULL \n RETURN COALESCE(user_row.first_name || ' ', '') || COALESCE(user_row.last_name, '');\n ELSE\n RETURN COALESCE(user_row.name, '');\n END IF;\nEND;\n$$ LANGUAGE plpgsql STABLE;<\/pre>\n\n\n\n
Issues you may encounter<\/h3>\n\n\n\n
whitelist.add({\n document: AddSurveyTranslationsDocument,\n check: hasOrganizationAdminGrant\n});\n\nwhitelist.add({\n document: GetManageAssignmentsDataDocument,\n authorize: ({ appUser, variables }) => {\n \/\/ Enforce that from front-end, user must query in his own behalf only\n return variables?.managerUserId === appUser.id;\n },\n allowedRoles: [HasuraRole.USER, HasuraRole.ADMIN]\n});<\/pre>\n\n\n\nKey takeaways<\/h2>\n\n\n\n