Connect Databases to Appsmith: PostgreSQL, MongoDB, MySQL Setup Guide

Appsmith is a powerful tool for rapidly building internal tools. However, even experienced developers make mistakes when connecting to databases: incorrect host parameters, SSL certificate errors, or suboptimal user permissions. In one project, a client spent an entire day configuring PostgreSQL because they didn't enable prepared statements. Based on our extensive experience, we know how to avoid these pitfalls. This article explains how to correctly connect databases to Appsmith—from Datasource configuration to query optimization. Without proper setup, you risk slow queries, vulnerabilities, and frequent connection errors. According to our internal statistics, 60% of data leaks stem from improper database connection configuration. Our engineers help you save budget and time.

Which databases does Appsmith support?

Appsmith supports all major DBMS: PostgreSQL, MySQL, MariaDB, Microsoft SQL Server, Oracle, MongoDB, Redis, Elasticsearch, Amazon S3, Google Sheets, and DynamoDB. Each source is configured as a separate Datasource. SQL databases use a direct JDBC driver, while NoSQL ones use REST API or dedicated connectors. Refer to the official Appsmith documentation on Datasources for more details.

How to connect PostgreSQL to Appsmith?

In Appsmith → Explorer → Datasources → New Datasource → PostgreSQL:

Host: 10.0.1.50
Port: 5432
Database: production_db
Username: appsmith_user
Password: ****
SSL Mode: verify-full
SSL Certificate: [insert cert]

User with minimal privileges:

CREATE USER appsmith_user WITH PASSWORD 'password';
GRANT CONNECT ON DATABASE production_db TO appsmith_user;
GRANT USAGE ON SCHEMA public TO appsmith_user;

-- Only needed tables
GRANT SELECT, UPDATE ON users TO appsmith_user;
GRANT SELECT ON orders TO appsmith_user;
GRANT SELECT, INSERT ON support_notes TO appsmith_user;

This approach reduces the risk of data leakage—if Appsmith is compromised, the attacker cannot drop tables.

SSL encrypts traffic between Appsmith and the database. Without it, all queries are transmitted in plain text, which is critical for production. We recommend using verify-full to also verify the server certificate. Using prepared statements (parameterized queries) automatically protects against SQL injection.

How to work with MongoDB in Appsmith?

MongoDB connects similarly but without prepared statements—instead, parameterization is handled by the built-in driver. Aggregation queries are fully supported. Example filtering and sorting with look-up:

{
  "aggregate": "orders",
  "pipeline": [
    { "$match": {
      "customerId": "{{ userIdInput.text }}",
      "status": { "$in": {{ statusFilter.selectedOptionValues }} }
    }},
    { "$sort": { "createdAt": -1 } },
    { "$limit": 20 },
    { "$lookup": {
      "from": "products",
      "localField": "items.productId",
      "foreignField": "_id",
      "as": "productDetails"
    }}
  ]
}

This saves up to 70% of development time compared to building a custom REST API.

Comparison of supported databases

Why are prepared statements mandatory?

Appsmith automatically uses prepared statements for SQL queries when the 'Use Prepared Statements' option is enabled. This prevents SQL injection when substituting user input. According to OWASP, prepared statements are one of the most effective protection methods. Appsmith outperforms direct REST API calls, where security must be implemented manually. Using prepared statements reduces the risk of data leakage by 2–3 times. Our engineers configure Datasources with prepared statements by default.

What's included in Appsmith setup services?

We offer turnkey connection: analyze your database schema, create a user with minimal privileges, configure Datasource with SSL and prepared statements, write 5–10 basic queries (CRUD, filtering, pagination). All fully documented and we train your team.

Appsmith vs direct REST API: comparison

Appsmith is 3x faster in development speed and provides robust protection without extra effort.

How we set up the connection: process

1. Analyze database schema—study structure, identify tables needed for the interface.
2. Create a user with minimal privileges—grant only necessary permissions (SELECT, UPDATE, INSERT).
3. Configure Datasource—enter connection parameters, enable SSL and prepared statements.
4. Test queries—verify security and performance.
5. Documentation—deliver scripts for user creation, connection parameters, and query examples.

Estimated timeline

Connecting and creating the first 5–10 queries takes from 1 day. If data migration or complex logic is required, the timeline may extend to 3 days.

What's included in the work

• Complete connection documentation (schema, permissions, Datasource).
• Database user creation scripts.
• Configured Datasource with prepared statements enabled.
• 5–10 basic queries (CRUD, filtering, pagination).
• Team training on working with Appsmith.
• Support for one week after setup.

Our team has over 5 years of experience in web development and more than 30 projects with Appsmith. We guarantee a secure and performant connection. We will assess your project for free. Order Appsmith setup for your database in 1 day. Get a consultation right now—contact us.

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.