How We Built a Library of Prebuilt Microservices That Cuts IT Product Development Time by 2-3x

Introduction: The Hidden Bottleneck in Product Development

In the world of IT product development, speed is often the difference between success and failure. But here’s the reality: before your team even touches the unique features that make your product special, you spend months building the same things over and over again - user authentication, permissions, file storage, payment integration, notifications, content management…

It’s not glamorous work, but without it, nothing else functions. And in fast-moving markets, those months can cost you your competitive edge.

At Lomray Software, we faced this problem on every project. Until we decided to solve it once and for all.

The Idea: Build Once, Use Everywhere

After repeating the same backend groundwork across dozens of projects, we asked ourselves a simple question: If 80% of modern backend features are standard, why are we rebuilding them from scratch every time?

Our answer was to create a library of prebuilt microservices - modular, battle-tested components that could be combined like Lego bricks to form a reliable backend infrastructure.

The result?

2-3 months saved in development time
More stable and maintainable code
Freedom to focus on the features that matter most to users

Architecture and Principles

From the start, we built these microservices with a clear philosophy:

Single Responsibility - each microservice solves one task and does it well
Event-Driven Communication - services interact via events for scalability
JSON-RPC Protocol - fast, structured inter-service communication
Centralized Logging and Monitoring - better observability and debugging

Core tech stack:

Node.js & TypeScript
PostgreSQL
Express & TypeORM

Categories of Microservices

We’ve organized our library into four main categories:

1. Users & Access

Authentication - including OAuth via Google, Facebook, and more
Authorization - role-based access control
User Management - profiles, restrictions, blocking

2. Communication & Content

Notification - email and push notifications
Blog - posts, tags, rich text editor
Content - SEO settings, static pages

3. Payments & Files

Payment-Stripe - payments, subscriptions, transactions
Files - uploads and storage, S3-compatible

4. Infrastructure

Gateway - routing, validation, logging
Configuration - centralized settings
Cron - scheduled background tasks

Real-World Application: From Zero to Launch in Less Than 2 Months

Case: An online stand-up comedy platform for live streaming shows and audience interaction.

Requirements:

Live streaming to thousands of users
Real-time reactions and comments
User accounts and roles
Media storage and notifications
Admin tools for content management

Our Approach:

Deployed 8 prebuilt microservices (auth, users, notifications, files, content, etc.)
Configured a gateway for routing, authorization, and logging
Built streaming-specific business logic on top of the ready-made backend framework

Outcome:

Backend completed in under 2 months
Stable performance under peak live-event loads
Easy scaling and rapid addition of new features

Who Benefits the Most

This approach is particularly effective for:

Startups & MVPs racing to validate their idea before competitors
B2B products with strict compliance or uptime requirements
Digital agencies tired of rebuilding the same core features
IT companies aiming to shorten time-to-market without sacrificing quality

Conclusion: From Plumbing to Progress

By rethinking backend development, we’ve transformed the way we deliver IT products. Instead of sinking months into repetitive setup, we start every project with a proven foundation - freeing our time, budget, and energy for what truly matters: creating features that users love.

The lesson? Sometimes innovation isn’t about inventing something new - it’s about stopping the reinvention of what’s already been solved.

If you’re planning to launch a product and don’t want your first 12 weeks consumed by boilerplate work, let’s talk.