Challenges: Splitting legacy Java applications to micro-services with a new public Node.js layer
eHarmony.com recently embarked on a technological journey that many enterprise software teams have come to realize: converting consumer-facing legacy applications to a Node.js stack will provide more stability, efficiency, and throughput for handling high-traffic environments. Stace Baal, the Director of Engineering at eHarmony.com, was faced with the challenge of splitting an existing Java layer into Node.js and Java while simultaneously ensuring zero downtime for the application and a rich user experience for their users.
While operating within a new service-oriented architecture with micro-services, Baal was faced with the challenge of monitoring multiple technology stacks while ensuring key metrics remain above critical thresholds.
Having a disconnect among the distributed teams became risky in tracking latency and errors among a distributed transaction. Baal soon came to realize there were too many dashboards with decoupled monitoring solutions causing an inefficiency in productivity. “Before a product such as AppDynamics, it used to take several people looking at several different monitoring solutions, comparing numbers to find any problem with our system.”