18F / its70-fs-epermit-scale-up

Solicitation for Schedule 70 vendors to support the U.S. Forest Service ePermit app
3 stars 4 forks source link

Technology Stack #15

Open td-variq opened 6 years ago

td-variq commented 6 years ago

Question/Comment on the Forest Service RFP

Name and affiliation

Thomas Delrue, Lead Software Architect, VariQ Corporation

Section of RFP documents

Technology Stack

Question/Comment

It will be helpful if you could include a high-level architecture of the system and target-state/preferred technology stack. Part of our confusion stems from some references in the SOW talking about "modernization" and "migration", as well as API development. The SOW only contains references to front-end technologies (specifically node.js and AngularJS). A code review of the published github repository unveiled a few more, but we didn't see any back end/API/web service/micro-service code or referenced languages, libraries or frameworks. This may be a reflection of the current state of the system - some modernization programs do start with overhauling the UI while still connecting to the legacy APIs. We don't know if that is the goal and desired outcome, or if there is a plan to rebuild the APIs and potentially even migrate the database. Some discussion around this will help us and other vendors in providing more holistic solutions and approaches.

hannahkane commented 6 years ago

The stack referenced is what the continuing product will be developed in. For reference, node.js is the backend technology for the API driven services. Both the server directory of the main repository as well as the entire middlelayer API repository comprise the backend code and architecture. The target state of the application will evolve as this an agile project, though a current state of the architecture is available in our public project wiki.

The migration and modernization referred to in the RFP refers to the creation of an online process rather than a migration from a current online permitting service.