Remote Config Setup for Dynamic Site Parameter Management

Rolled out a new file upload limit requiring a full frontend deploy? Each update takes hours, and emergency disabling a broken feature costs minutes of downtime. On a production project with 50,000 DAU, we needed to disable a feature urgently—without Remote Config it would have taken 2 hours via CI/CD. With Remote Config, the switch took 5 seconds.

We help set up Remote Config so you can change parameters through a web interface—in real time, without rebuild or release. Approaches: Firebase, Flagsmith (self-hosted), and custom implementation—with code, configs, and typical scenarios. This article covers concrete implementations, configs, and advice based on 10+ years of production experience.

Why Remote Config is a must-have for modern sites

Feature flags without deploy. Releasing a new form? With Remote Config, enable it for 10% of users first, then for everyone after debugging. Without it, you need to rebuild the build, which takes on average 30 minutes instead of a second-long flag toggle.

Change limits on the fly. Bot attack? Reduce API request limits from 100 to 20 per minute without touching code. Or increase max file size for premium accounts.

Manage texts and UI. Need an urgent banner? Remote Config updates the text in seconds, without deploying translations.

We have implemented Remote Config in projects with audiences from 10,000 to 500,000 DAU (over 15 projects)—the scheme proved reliable. Our experience guarantees stability: cache hit rate 95%, zero config inconsistency.

How to choose a provider: Firebase, Flagsmith, or custom?

Firebase Remote Config integrates 2x faster than Flagsmith, but Flagsmith gives more control: user segments, A/B tests, and self-hosted hosting. Custom offers full control but requires development. The choice depends on stack and data residency requirements. For example, for fintech with data storage policies in Russia—Flagsmith or custom.

How often to update config without breaking the app?

The optimal fetch interval is 5–10 minutes. Too frequent fetching creates load and delays. Always set fallback values in code—if the server is unavailable, the app won't break. Use server-side caching with TTL: Redis or in-memory cache. For an API server, latency dropped by 15% after setting up tag-based cache invalidation.

How to ensure Remote Config security?

Secure Remote Config setup includes access control to the management panel, encryption in transit (TLS), and config signing to prevent tampering. For custom solutions, use HMAC verification. In Flagsmith—role-based model and audit log.

How we do it: stack and configs

Firebase Remote Config

Quick start for Firebase projects:

npm install firebase

// lib/remoteConfig.ts
import { initializeApp } from 'firebase/app';
import { getRemoteConfig, fetchAndActivate, getValue } from 'firebase/remote-config';

const app = initializeApp({
  apiKey: process.env.NEXT_PUBLIC_FIREBASE_API_KEY,
  projectId: process.env.NEXT_PUBLIC_FIREBASE_PROJECT_ID,
  appId: process.env.NEXT_PUBLIC_FIREBASE_APP_ID,
});

const remoteConfig = getRemoteConfig(app);
remoteConfig.settings.minimumFetchIntervalMillis = 300_000;

remoteConfig.defaultConfig = {
  maintenance_mode: false,
  max_upload_size_mb: 10,
  welcome_banner_text: 'Welcome!',
  new_dashboard_enabled: false,
  max_api_calls_per_minute: 60,
};

export async function initRemoteConfig() {
  await fetchAndActivate(remoteConfig);
}

export function getConfig<T>(key: string): T {
  const value = getValue(remoteConfig, key);
  if (typeof remoteConfig.defaultConfig[key] === 'boolean') {
    return value.asBoolean() as T;
  }
  if (typeof remoteConfig.defaultConfig[key] === 'number') {
    return value.asNumber() as T;
  }
  return value.asString() as T;
}

According to Firebase official documentation, the minimum fetch interval is 300 seconds, optimal for most scenarios. In components, call getConfig inside useEffect—the example is trivial. Fast integration, free tier (24,000 tests/day), but tied to Firebase, no on-premise.

Self-hosted: Flagsmith

Open-source alternative for your own servers, ideal for data residency:

# Docker Compose
services:
  flagsmith:
    image: flagsmith/flagsmith:latest
    environment:
      DATABASE_URL: postgresql://flagsmith:secret@db/flagsmith
    ports:
      - "8000:8000"

import Flagsmith from 'flagsmith-nodejs';

const flagsmith = new Flagsmith({
  environmentKey: process.env.FLAGSMITH_ENV_KEY!,
  enableLocalEvaluation: true,
  environmentRefreshIntervalSeconds: 60,
});

async function getConfig(userId: string, userPlan: string) {
  const flags = await flagsmith.getIdentityFlags(userId, {
    plan: userPlan,
    country: 'RU',
  });

  return {
    maxUploadSizeMb: flags.getFeatureValue('max_upload_size_mb', 10),
    betaFeatures: flags.isFeatureEnabled('beta_features'),
    apiRateLimit: flags.getFeatureValue('api_rate_limit', 100),
  };
}

Flagsmith supports segments, A/B tests, integration with any language. We deployed it for 7 projects—no failures, deployment time from 2 to 3 days.

Custom solution via API

Full control if you have a DB and admin panel:

// Store config in DB
// config table: key (varchar), value (jsonb), updated_at

// API endpoint
// GET /api/config → returns current parameters

// Server-side caching
import { unstable_cache } from 'next/cache';

const getRemoteConfig = unstable_cache(
  async () => {
    const configs = await db.config.findMany();
    return Object.fromEntries(configs.map(c => [c.key, c.value]));
  },
  ['remote-config'],
  { revalidate: 300 }
);

// Invalidate cache on update
async function updateConfig(key: string, value: unknown) {
  await db.config.upsert({
    where: { key },
    create: { key, value },
    update: { value, updatedAt: new Date() },
  });
  revalidateTag('remote-config');
}

Custom gives flexibility but requires 3–5 days and thorough caching testing.

Comparison of approaches

Work process for implementation

1. Analysis—study architecture, identify parameters to externalize.
2. Design—select provider, design config structure and caching.
3. Implementation—write SDK, connect frontend and backend, set up admin panel.
4. Testing—verify value correctness, delivery speed, fallback.
5. Deployment and documentation—staging, production, team instructions.

Timelines and what's included

Estimated timelines: Firebase or Flagsmith—1–3 days; custom—3–5 days. Exact timeline after audit—contact us for a free assessment. The cost includes: SDK setup, configs, UI panel, documentation, team training, 2 weeks of support. We guarantee stable operation—all solutions battle-tested. Save up to 40 deployment hours per month (≈ $1,700 at $42/hr). Infrastructure cost reduction up to 30% (≈ $700 per month).

Typical Remote Config parameters

Conditional targeting: different values for different users. Beta users—newCheckoutEnabled: true. Pro accounts—maxUploadSizeMb: 100. Administrators—maintenanceMode not applied.

How to avoid common mistakes

• Too frequent fetch—load and delays. Optimum: 5–10 minutes.
• No fallback defaults—without them, the app breaks when server is unavailable. Always set fallbacks.
• No server-side caching—each request hits the DB. Use Redis or in-memory cache with TTL.

Contact us for a free consultation and project assessment. Order Remote Config implementation and get documentation and team training. We guarantee stability and fast start.

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.