Real Estate platform Upgrade

A picture of Earth at night with abstract paths around the globe - System architecture diagram illustrating API integration and data consolidation - Travel technology case study by Brightgrove

Real Estate Broker Platform — ASP.NET to React & Elasticsearch Migration

How Brightgrove modernized a real estate broker platform — ASP.NET MVC to React/Redux migration, Elasticsearch as primary data store, MS SQL CDC event sync, backward-compatible.

Real Estate

Cloud

Microservices

Home

Our Experience

Real Estate platform Upgrade

Home

Our Experience

Real Estate platform Upgrade

Client profile

The real estate platform serves as a backbone for the day-to-day real estate broker operations as well as provides overview and detailed reports on the past and current real estate market state. The system not only serves data to real estate brokers, it allows both updating existing listing data and syndication of listing data to various feeds.

Platform modernization solution

Our comprehensive platform upgrade strategy focused on three core components:

Core Technology Stack

• Moved to ASP.NET MVC/Core where possible

• Used React + Redux for client-side development

Architecture Improvements

• Moved away from database-contained logic to back-end C# code without performance losses (and sometimes with improvements)

• Reused existing assets in more creative and efficient ways, i.e.:

• Used Elasticsearch as a primary data store for a few business-important systems, not only search cache tool

• Used MS SQL CDC (Change Data Capture) feature to build event-based synchronization system

• Added solid middle layer to compose various lower-level business operations

• Re-used backend and front-end functionality using internal NuGET and npm packages

Core Technology Stack

• Moved to ASP.NET MVC/Core where possible

• Used React + Redux for client-side development

Architecture Improvements

• Moved away from database-contained logic to back-end C# code without performance losses (and sometimes with improvements)

• Reused existing assets in more creative and efficient ways, i.e.:

• Used Elasticsearch as a primary data store for a few business-important systems, not only search cache tool

• Used MS SQL CDC (Change Data Capture) feature to build event-based synchronization system

• Added solid middle layer to compose various lower-level business operations

• Re-used backend and front-end functionality using internal NuGET and npm packages

Core Technology Stack

• Moved to ASP.NET MVC/Core where possible

• Used React + Redux for client-side development

Architecture Improvements

• Moved away from database-contained logic to back-end C# code without performance losses (and sometimes with improvements)

• Reused existing assets in more creative and efficient ways, i.e.:

• Used Elasticsearch as a primary data store for a few business-important systems, not only search cache tool

• Used MS SQL CDC (Change Data Capture) feature to build event-based synchronization system

• Added solid middle layer to compose various lower-level business operations

• Re-used backend and front-end functionality using internal NuGET and npm packages

Performance Optimizations

• Rendered only visible portions of data and fine-tune requests to server to return as much data as needed for the single viewport

• Recomposed existing products in a way which enables new business scenarios and opens new sources of revenue

Performance Optimizations

• Rendered only visible portions of data and fine-tune requests to server to return as much data as needed for the single viewport

• Recomposed existing products in a way which enables new business scenarios and opens new sources of revenue

Implementation approach

Migration Strategy—Gradual Transition

• Module-based approach to transition not only front-end, but backend part as well at the same time. As a parallel process performance and security review and improvement conducted

• Parallel operation of old and new modules during transition

• Seamless integration of updated parts of functionality into legacy parts/pages

• Changes are always backward-compatible with existing systems

Migration Strategy—Gradual Transition

• Module-based approach to transition not only front-end, but backend part as well at the same time. As a parallel process performance and security review and improvement conducted

• Parallel operation of old and new modules during transition

• Seamless integration of updated parts of functionality into legacy parts/pages

• Changes are always backward-compatible with existing systems

Migration Strategy—Gradual Transition

• Module-based approach to transition not only front-end, but backend part as well at the same time. As a parallel process performance and security review and improvement conducted

• Parallel operation of old and new modules during transition

• Seamless integration of updated parts of functionality into legacy parts/pages

• Changes are always backward-compatible with existing systems

Conclusion

Brightgrove delivered a fully modernized real estate broker platform using a module-by-module gradual migration approach — maintaining backward compatibility throughout and running old and new modules in parallel to eliminate downtime risk. The updated architecture moved business logic from database-contained procedures to a clean C# backend, introduced Elasticsearch as a primary data store for business-critical systems, and implemented MS SQL Change Data Capture for reliable event-based synchronization.