Skip to content
Rearway logorearwayLet's talk ↗

Services · Backend & cloud engineering

Backend & Cloud Engineering

Book a call for a quote ↗

01

The problem

  • Built by hand: infrastructure set up manually in the console, impossible to reproduce or review.
  • Unpredictable APIs: slow under load, and inconsistent or poorly documented.
  • Wrong-fit databases: the wrong database for the access pattern, leading to slow queries or high bills.
  • Not enough visibility: no monitoring, alerting or tested backups.
  • Security gaps: over-permissive IAM roles, secrets kept in code, public storage.

02

What we do

API and service development

  • API design: REST and GraphQL APIs, designed contract-first with OpenAPI.
  • Languages: services in Node.js/TypeScript, Python or Go.
  • Built in from the start:
    • authentication and authorisation (OAuth 2.0 / OIDC, role and object-level checks)
    • rate limiting and validation
    • idempotency
  • Async processing with queues and pub/sub (SQS/SNS, Pub/Sub, EventBridge) for background jobs and integrations.
  • Third-party integrations: payments, messaging, maps, CRMs and ERPs.

Data

  • Choosing the right store: PostgreSQL (RDS/Cloud SQL/AlloyDB), Firestore/DynamoDB for real-time or key-value access, Redis/Memorystore for caching, and BigQuery or Redshift for analytics.
  • Schema design: indexing, partitioning and clustering, and migrations.
  • Data pipelines and change data capture (CDC) where needed.

Cloud infrastructure

  • Compute: serverless (Cloud Run, Lambda) or containers (GKE, EKS, ECS), chosen to fit the workload. That includes scale-to-zero for services that don't need to run all the time.
  • Infrastructure as code: Terraform, with separate environments for dev, staging and production.
  • Networking: VPC design, private networking, load balancing, CDN and WAF.
  • Delivery: CI/CD pipelines with automated tests, security scans and safe deployment strategies (blue/green, canary).

Reliability and operations

  • Monitoring: logging, metrics, tracing (OpenTelemetry), dashboards and alerts linked to SLOs.
  • Backups and recovery: backups with tested restores, and a disaster recovery plan.
  • Capacity and load testing: see QA & Production Readiness.
  • Cost visibility from day one: labels, budgets and alerts. See Cloud Cost Audit.

Security by default

  • Access: least-privilege IAM.
  • Secrets: stored in Secret Manager or Secrets Manager.
  • Encryption: in transit and at rest.
  • Audit logging: CloudTrail / Cloud Audit Logs.
  • Benchmarks: configuration aligned with the CIS Benchmarks.

03

How it works

  1. Scoping call. We cover your product, current setup and goals.
  2. Architecture design. Diagrams, technology choices and their trade-offs, written up as decision records.
  3. Foundation. Environments, infrastructure as code, CI/CD and monitoring.
  4. Build in sprints. Working APIs and services delivered incrementally.
  5. Hardening. Load, security and recovery testing.
  6. Handover or ongoing support.

04

What you receive

  • Architecture documentation: C4 diagrams and decision records.
  • Source code and infrastructure as code in your repositories.
  • API documentation (OpenAPI).
  • CI/CD pipelines, monitoring dashboards and alerts.
  • Runbooks for deployment, incidents and recovery.
  • Test and security review results.

05

Standards and tools

Aligned with: the AWS Well-Architected Framework, the Google Cloud Architecture Framework, the Twelve-Factor App, the OWASP API Security Top 10, and the CIS Benchmarks for AWS and Google Cloud.

Tools:

  • Infrastructure and delivery: Terraform, Docker, Kubernetes, GitHub Actions / Cloud Build
  • Observability: OpenTelemetry, Grafana, Cloud Monitoring, CloudWatch
  • Databases: PostgreSQL, Redis, BigQuery

06

Packages

We offer fixed-price packages for businesses with different needs. Scope, timeline and deliverables are agreed in writing after the scoping call.

07

Next step

Book a 30-minute call to talk through your product and what you need.

Book a call

FAQ

Questions

AWS or Google Cloud, which should we use?

Both work well. We recommend based on your existing setup, team skills, the managed services you need, and data residency.

Serverless or Kubernetes?

Serverless (Cloud Run, Lambda) suits most new products: less to operate and the ability to scale to zero. Kubernetes makes sense for complex, steady workloads or specific platform needs. We explain the trade-off for your case.

Can you work on our existing infrastructure?

Yes. We often start by bringing existing resources into Terraform, adding monitoring, and fixing security gaps, then build from there.

Will you have access to our production environment?

Only what's agreed, through least-privilege roles in your accounts. Changes go through pull requests and pipelines, not console edits.

How do you keep cloud costs under control?

We size for actual usage, use scale-to-zero where it fits, set budgets and alerts, and review costs as part of delivery.

Do you provide ongoing support?

Yes. We can provide ongoing development and operations support, or hand over fully with runbooks and training.

Start a project

Have a product to ship?

Engagements are fixed-price packages, shaped to the business. Book a call for a quote.

Book a 30-min call ↗