Lecture: Migrating Frontend Code from A Monolith to Microservices

As the business requirements for Yelp for Business Owner Application change constantly, our old frontend stack built on top of Google Closure and jQuery is no longer the best choice. Besides, a large part of the application code still lives in a monolith repository which has a large overhead with regard to testing and development.

As one of the feature teams, we want to migrate our frontend code to a frontend service built on top of the React ecosystem to ease future development and deployment.

But a big bang rewrite is not a option because new feature development should not be halted by this migration. How should we build the bridge between the old tech stack and the new tech stack? How should we combine new feature development and migration? How can we guarantee the functionality won’t be changed and no bugs get introduced by the migration?

As the business requirements for Yelp for Business Owner Application change constantly, our old frontend stack built on top of Google Closure and jQuery is no longer the best choice. Besides, a large part of the application code still lives in a monolith repository which has a large overhead with regard to testing and development.

As one of the feature teams, we want to migrate our frontend code to a frontend service built on top of the React ecosystem to ease future development and deployment.

But a big bang rewrite is not a option because new feature development should not be halted by this migration. How should we build the bridge between the old tech stack and the new tech stack? How should we combine new feature development and migration? How can we guarantee the functionality won’t be changed and no bugs get introduced by the migration?

Info

Day: 2018-10-06
Start time: 14:40
Duration: 00:55
Room: G 61
Track: Computer Science

Links:

Feedback

Click here to let us know how you liked this event.

Concurrent Events