Secure PostgreSQL, MySQL, MongoDB Connections in Retool

When setting up Retool for internal tools, common issues arise: incorrect permissions, insecure connections, and N+1 queries that kill performance. A typical scenario: a developer grants the database superuser access and then wonders why data leaks. Or connects MongoDB without SSL, leaving traffic in plaintext. Recently, a client lost 2 days deploying an admin panel due to incorrect permissions — we fixed it in 3 hours. We set up database connections (PostgreSQL, MySQL, MongoDB) from scratch: from creating a dedicated user to configuring an SSH tunnel. Below are typical configs, best practices, and real pitfalls we avoid.

Problems We Solve

N+1 queries are a major cause of slowdowns. Retool without caching can execute dozens of queries to render a single widget. For example, a list of customers with their orders: without joins, you get 1 query per customer + N for orders. This increases load time by 500%. The solution: use parameterized queries with LEFT JOIN inside a single call.

Insecure connections — a database with a public IP, a superuser password in plaintext, and no SSL. In one project, we found that MongoDB could be connected without a password from anywhere in the world. We had to urgently change the settings.

Permissions — often roles are too broad. This leads to accidental data deletion or SQL injections. We always create a user with minimal privileges.

Avoiding N+1 Queries

N+1 occurs when for each parent object, a separate child query is executed. In Retool, this is especially noticeable in tables with lookups. The optimal approach is a single SQL query with JOIN, aggregation, or IN () expressions. For example, instead of:

SELECT * FROM customers; -- 1 query
-- for each customer:
SELECT * FROM orders WHERE customer_id = $1;

Use:

SELECT c.*, o.order_count
FROM customers c
LEFT JOIN (
  SELECT customer_id, COUNT(*) as order_count
  FROM orders
  GROUP BY customer_id
) o ON c.id = o.customer_id;

Typical latency from N+1 is 2-3 seconds per page. After optimization, the query runs in 50 ms.

Connecting PostgreSQL, MySQL, and MongoDB

Retool supports popular databases. We'll cover connecting each. Important: all connections must be encrypted, and users must have limited privileges.

PostgreSQL

Follow these steps to connect PostgreSQL:

1. Create a resource in Retool: Resources → Create New → PostgreSQL.
2. Provide your database hostname (e.g., your-database-server.com), port 5432, database name, a read-only username, and password.
3. Set SSL mode to require.
4. Create a dedicated read-only user using the SQL example below.

Example SQL to create a read-only user:

CREATE USER retool_readonly WITH PASSWORD 'secure_password';
GRANT CONNECT ON DATABASE app_production TO retool_readonly;
GRANT USAGE ON SCHEMA public TO retool_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO retool_readonly;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO retool_readonly;

MySQL

For MySQL, also use a separate read-only user. Enable SSL: Required and set charset to utf8mb4. Default port is 3306.

MongoDB

Connection string: mongodb://user:pass@host:27017/db?ssl=true. In production, use a replica set with retryWrites=true. Default port is 27017.

SSH Tunnel Configuration

If the database does not have a public IP, use an SSH tunnel. Retool supports setting it up in a few minutes.

1. On the bastion server, create a user retool-tunnel with restricted commands.
2. When creating a resource in Retool, enable SSH tunnel and specify:
   • SSH host: your-bastion-host
   • SSH port: 22
   • SSH username: retool-tunnel
   • SSH private key: your SSH private key
3. On the bastion server, restrict commands:

Match User retool-tunnel
  ForceCommand /bin/false
  PermitTunnel yes
  AllowTcpForwarding yes

Parameterized Queries vs. SQL Injections

Retool automatically escapes variables in {{ }}. Always use them. Example of safe update:

UPDATE users
SET status = {{ statusSelect.value }},
    updated_at = NOW(),
    updated_by = {{ current_user.email }}
WHERE id = {{ usersTable.selectedRow.data.id }}
  AND status != {{ statusSelect.value }}

Never concatenate strings manually — that is a direct path to injections. According to Retool Documentation, parameterized queries are the only safe method.

Access Permissions for Retool

It is best to create a separate read-only user. If writes are needed, grant rights only to specific tables. Example for PostgreSQL:

GRANT SELECT, UPDATE ON users TO retool_ops;
GRANT SELECT, INSERT, UPDATE ON orders TO retool_ops;

Turnkey Setup: What's Included

We provide a full cycle of work:

• Architecture analysis and optimal stack selection
• Creating database users with minimal privileges
• Configuring SSH tunnel and SSL
• Configuring resources in Retool
• Writing the first 5–10 queries and widgets
• Documentation on connection and security
• Team training (1 hour)

Timeline — from 1 day. Cost is calculated individually based on complexity. Typical pricing for a turnkey Retool setup under key starts at $800 and includes all steps above. For Retool optimization, we recommend regular performance audits and connection pooling.

Common Setup Mistakes

• Incorrect host: use private IP if Retool and database are on the same network.
• Missed firewall: check that Retool's IP is allowed in security group.
• Wrong port: verify with the DBA.
• Missing SSL: always enable SSL mode require or ssl=true.

Why Trust Us with Setup?

We have 5+ years of experience with Retool and databases. We guarantee security and performance. We have configured over 50 projects. Retool is 5x faster than custom admin panels — you save up to 40% development time. Get a consultation — we will assess your project.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.