Separation of Front End and Back End
  

Updated Jun 15, 2018

2 To do

2 To Validate

1 In progress

0 Done

This project doesn’t have any columns or cards.

Menu

Separation of Front End and Back End #5

  
Updated Jun 15, 2018
Goals is to separate front end and back end and remove the current tight coupling between the two.

Goals is to separate front end and back end and remove the current tight coupling between the two.

The back end will expose OpenRefine core functionality via an API. Once the decoupling done, we can support Apache Beam to allow batch processing via different engines. OpenRefine will support by default one (or two) engine that allows users to run OpenRefine on their local machine. Other teams can integrate with Spark for distributed computing supported by Beam. See also the Performance Improvements project

The front end will be migrated in a modern javascript framework (angular? react? something else?) and enable us to tackle the UI Improvement project

Activity

    Loading activity

Archived cards

Loading archived cards…