Cutting video infrastructure costs on a platform built for doctors
A platform where doctors access video education, a social feed and peer consultation. Beyond backend delivery, a custom video transcoding service replaced a managed cloud service to bring running costs down.
- Client
- HN Healthcare
- Sector
- Healthcare — professional education and consultation
- Duration
- 3+ years
- Role
- Core backend developer and product manager
- Transcoder replacing managed service
- In-houseTranscoder replacing managed service
- Socket-based data updates
- Real timeSocket-based data updates
- Continuous ownership
- 3+ yearsContinuous ownership
01 — Problem
What was going wrong
The product gave doctors a single place to learn and talk to each other: a video education library, a social feed, and consultation between practitioners. Each of those carries a different technical demand.
Video was the expensive one. The education library meant continuously processing video into deliverable formats, and the managed cloud transcoding service handling it had become a significant line item on the running cost of the product.
At the same time, the consultation and feed features needed to feel immediate — which a conventional request-response backend does not provide on its own.
02 — Investigation
What the evidence showed
The video cost was examined as an engineering problem rather than accepted as a fixed cost of doing business. The question was what the managed service was actually providing that the platform needed, and how much of it was general-purpose capability this product would never use.
The real-time requirements were scoped the same way: which interactions genuinely needed live updates, and which only appeared to.
03 — Solution
What was built
A video transcoding service was built in-house, mirroring the behaviour of the managed AWS transcoder for the specific formats and workflows the platform actually required. Purpose-built for one product's needs, it avoided paying for a general-purpose service's full surface area.
Real-time features were delivered using NodeJS with socket-based communication alongside the Laravel API, so data changes reached users immediately where that mattered.
The role spanned both engineering and product. Working as a core developer and product manager meant technical and product decisions were made with full knowledge of each other — including this one, where an engineering choice was driven by a commercial constraint.
04 — Result
What changed
The in-house transcoder brought the video processing cost of the running product down while continuing to serve the education library.
Doctors got a platform where education, discussion and peer consultation worked together, with real-time behaviour where it counted.
Three years of continuous ownership meant decisions were made by someone who would still be there to live with them.
Technologies involved
- Laravel
- NodeJS
- WebSockets
- Video transcoding
- AWS
- REST APIs
Related services
Have a software problem, project or idea?
Tell me what you are trying to achieve and where it is currently going wrong. You will get an honest read on it from someone who has built this kind of thing before — including if the answer is that you do not need what you were about to buy.
Prefer not to call? Send me a message
Working with businesses across Australia — Melbourne, Sydney, Brisbane, Adelaide, Perth, Canberra and regional Australia.