Confidential client, name withheld under NDA

In-House Hospital Management System Modernization Using Golang

Quick answer: Moving only the patient monitoring module of a hospital system to Go lets it hold thousands of device connections on fewer servers. Bacancy did this for a US hospital network's in-house platform, while Node.js runs the rest.

Outcomes deliveredDelivered January to March 2026 by a team of 4 engineers
3x

Faster monitoring response at peak

Peak-hour connection queuing removed

7x

Fewer peak-hour service outages

Uptime held at 99.9%+

35%

Fewer servers at peak load

35 to 40% fewer, lowering infra cost

0

Disruption to the Node.js core

Strangler-fig cutover, system stayed live

Client name withheld under NDA. To honour our non-disclosure agreement and compliance obligations, we describe this client by industry and region only. The project scope, technology and outcomes are shared without details that could identify them.

About the Client

The client is a US hospital network's in-house hospital management system for patient records, scheduling and continuous patient monitoring. Its Node.js core ran records and administrative work well.

The monitoring module strained as thousands of devices streamed vitals during peak hours, and slow responses could affect patient care. Scaling Node.js kept adding servers. A full rewrite of a live hospital system was too risky.

A team of 4 Bacancy engineers moved only the monitoring module to Go microservices behind a shared API gateway, using the strangler-fig pattern. Responses are about 3x faster at peak, and outages fell about 7x. The module now needs 35 to 40% fewer servers.

Client type
Hospital network
Industry
Healthcare
Location
USA
Team
4 engineers
Timeline
January 2026 to March 2026
Project size
Non-disclosable

Three risks in a live hospital system

Peak device traffic, rising server needs and a no-downtime rule shaped every decision.

Slow monitoring at peak

What was happening

Thousands of devices held open connections and streamed vitals at peak hours.

Business Impact: Slow responses could delay how staff see patient vitals.

Growing server footprint

What was happening

Each Node.js process used more memory per connection than needed.

Business Impact: Horizontal scaling kept raising server counts and costs.

No room for a rewrite

What was happening

The hospital system was live, and its other modules worked well.

Business Impact: Any change had to be gradual, isolated and reversible.

Challenges & Solutions

Our engineers measured first, then changed only the module under real pressure.

Challenge 1: Finding where the pressure really was

The monitoring module struggled at peak, but the cause and scope were unclear.

Solution: Our engineers profiled the system before changing anything. Records and admin modules were healthy on Node.js, and only monitoring was under real concurrency pressure.

Challenge 2: Choosing Go only where it helps

Scaling Node.js horizontally kept adding servers because of memory used per connection.

Solution: Our healthcare developers tested clustering and horizontal scaling first. They chose Go only for monitoring, where goroutines hold many connections at low memory cost.

Challenge 3: Rebuilding the monitoring module

Real-time monitoring paths had to improve without touching the working Node.js modules.

Solution: Our Golang developers rebuilt monitoring as Go microservices that each hold thousands of device connections on one instance. The same load now runs on 35 to 40% fewer servers.

Challenge 4: Migrating with the system live

A full rewrite of a live hospital system was too risky.

Solution: Our team used the strangler-fig pattern behind an API gateway. Go and Node.js services run side by side and exchange data over REST and gRPC, with no disruption to clinical workflows.

How the Platform Works

The client project snapshot

Core Features

  • Go microservices for patient monitoringThousands of concurrent device connections per instance.
  • Node.js and Go behind one gatewayRecords and admin stay on Node.js; monitoring runs on Go.
  • REST and gRPC data exchangeBoth environments share data with no change for clinical staff.
  • Strangler-fig cutoverGradual, reversible migration with zero downtime during cutover.

The stack behind the platform

Backend (migrated module)
Go
Backend (retained)
Node.js
Database
PostgreSQL
API communication
REST APIs | gRPC
Architecture
Microservices | Strangler-fig migration | API gateway

Ready to start?

2500+ projects delivered by Bacancy Technology

Get access to an experienced team of developers and engineers from Bacancy Technology, handpicked to ace your goals. Kickstart within 48 hours, no-risk trial.

Book A 30 Min Call
14+Years of business experience
1458+Happy customers
30+Countries with happy customers
1050+Agile-enabled employees

More Case Studies

View All Case Studies