April 2024 Summaries

The migration of the Auth service from Node.js to Go was undertaken to enhance performance, reliability, and scalability while reducing resource consumption. The process followed the strangler fig pattern, allowing a gradual transition where both Node.js and Go operated concurrently, with Go handling requests for already migrated endpoints. Performance benchmarks revealed significant improvements with Go, particularly in handling a higher volume of requests with lower latency and memory usage. Despite the initial resource demands of running a dual-process system, the Go process efficiently managed requests, showcasing better metrics compared to Node.js. The migration also aimed to decouple the Auth service from Hasura, allowing direct interaction with PostgreSQL, which simplifies configuration options for developers. While the transition is expected to be seamless for users, minor issues may occur as the rewrite involves intricate features, but the overall benefits in performance and resource efficiency are anticipated to outweigh these challenges.

The recent update introduces the availability of the settings page in the dashboard for local development via the CLI, enhancing configuration correctness, Infrastructure as Code (IaC), and environment replication. This advancement, which ported some cloud functionalities to the CLI, allows real-time updates to local files as settings are edited in the dashboard, with changes seamlessly tracked through Git. Nhost Run is also supported, enabling the configuration of local environments and services using the dashboard without losing the benefits of managing projects with the toml file. Secrets management is integrated, ensuring comprehensive settings handling. Future plans include achieving settings-parity with the toml file and improving usability, along with enabling overlay editing through the dashboard to streamline overlay management.

A new suite of advanced features for GraphQL APIs has been introduced to enhance both observability and security. The observability improvements include a "GraphQL" dashboard that displays crucial metrics such as request rate, duration, and failure rate, helping identify bottlenecks and issues more efficiently. On the security front, two significant enhancements have been made: the ability to disable Hasura's admin secret to prevent unauthorized access in case of a leak, and a feature to limit the nesting depth of GraphQL queries to avoid resource exhaustion and potential denial-of-service attacks. These features are initially available to members of the Teams and Enterprise plans, with further enhancements like caching and two-factor authentication being considered for future development.

This text discusses a feature allowing users to connect multiple social login methods to their account, maintaining the same user ID regardless of the authentication method chosen, even if the email addresses differ. It provides a step-by-step guide for integrating this functionality into an app, using GitHub as an example. The process involves enabling the desired authentication provider, generating a link using the SDK, verifying the connection through a query, and implementing these steps in a React application. This feature is particularly useful for apps that rely on authentication provider APIs, offering flexibility and ease for users who may have signed up with different emails.