Cloud-agnostic Newsql Service
You set up a cloud agnostic newsql service by running distributed nodes across multiple cloud providers. These nodes sync data with consensus rules while apps use standard SQL to read and write. Most teams start this setup by creating broad admin roles for their engineers and apps. Overly broad roles create big risks when someone runs a bad query across every region. How a cloud agnostic newsql service handles roles and permissions A distributed SQL database splits tables into small chunks an
Service-to-Service Authentication: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You set up a cloud agnostic newsql service by running distributed nodes across multiple cloud providers. These nodes sync data with consensus rules while apps use standard SQL to read and write. Most teams start this setup by creating broad admin roles for their engineers and apps. Overly broad roles create big risks when someone runs a bad query across every region.
How a cloud agnostic newsql service handles roles and permissions
A distributed SQL database splits tables into small chunks and spreads them across different servers. Each server holds a copy of the data and votes on every write request. This design lets your database survive when a whole cloud region goes offline. You do not have to rewrite your app logic to handle these splits.
To manage users, admins define database roles and grant read or write permissions on tables. The cluster copies these role rules to every node in every cloud region. When an engineer logs in, the local node checks their user role against the table. The node also checks network rules to see if the user IP is allowed.
Teams often connect their identity provider to map group names to database roles. An engineer logs in with their work account and gets a database role for their team. All nodes in the cluster trust this role and let the user run SQL statements.
Why native roles leave a gap during live sessions
Native database roles do a good job of deciding who can log into the cluster. They also block users from reading tables that belong to other teams. Encryption between nodes keeps data safe while it moves across public cloud networks. These built-in tools solve the basic problem of who can reach the database.
Still, a database role cannot tell if a single SQL statement is safe to run. Once an engineer logs in with write rights, they can drop rows or change records. A broad read role also returns every column in a table to the user screen by default. If a table holds emails, phone numbers, or card numbers, the user gets all of it.
Service-to-Service Authentication: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Sharing static passwords or long-lived keys across multiple clouds makes this problem much worse. Teams struggle to rotate these keys across every app and user machine on time. Native audit logs also sit on separate nodes, which makes it hard to review queries fast.
Managing multi-cloud queries and sensitive data
To keep production data safe, teams must inspect SQL statements before the database runs them. You should separate normal read work from risky write tasks during live sessions. Engineers need a way to query tables while masking rewrites matched fields in results. Rewriting emails, phone numbers, and national IDs in results stops raw data leaks on laptops.
For write tasks, teams can require a peer review before a change runs on the cluster. Instead of giving out full admin keys, you can approve one query at a time. Central logs should record who ran each query and when it happened across all clouds. This setup keeps your multi-cloud data safe without changing how your database nodes work.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev runs beside those services as an open-source proxy, a sidecar for your Postgres or API. It inspects requests coming in and results going back on the wire.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run. On responses, hoop.dev data masking rewrites matched sensitive values in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
What makes a NewSQL database different from traditional SQL?
Traditional SQL runs on one main server, while NewSQL spreads data across many active nodes. You keep ACID rules and standard SQL queries while gaining horizontal scale across regions.
How do teams handle latency across different cloud providers?
Teams place database nodes in regions that sit close to each other to cut network lag. They also pin specific data rows to regions where local users read and write most often.
How can we protect sensitive fields during engineer troubleshooting?
You can apply data masking rules that inspect query results before they reach the user. Masking rewrites matched fields like card numbers or emails in results while keeping other columns clear.