06. Technical architecture

6. Evaluate what tools and systems will be used to build, host, operate and measure the service, and how to procure them.

Link to corresponding item in JIRA: https://jira.informed.com:8443/browse/FCOLOI-159

Questions

• Describe the languages, frameworks, and other technical choices you've made in alpha, and how those will affect the decisions you make in beta.
• Describe the development toolchain that you would like to select for beta and why.

Evidence

Service Manager able to:

• describe the languages, frameworks, and other technical choices they’ve made in alpha, and how this will affect the decisions they make in beta.
• describe the development toolchain they would like to select for beta and why.

---

(link to tech architecture on google docs)

Design Principles:

*adopt open modular architecture allowing components and services to be swapped in or out thus avoiding vendor lock-in *actively identify opportunities for reuse of code within FCO and wider government *use open source technologies as standard and release all developed code under XXX open source licence (PMC to confirm) *adopt common development, configuration and release pipeline tooling in line with other FCO services where applicable

Describe the languages, frameworks, and other technical choices you've made in alpha, and how those will affect the decisions you make in beta.

*continue to use GOV.UK design prototype toolkit to rapidly iterate and test UX features *Node.js (web application framework written in JavaScript) *PostgreSQL (relational database provider for Application Service) *Mocha (a Node.js unit testing framework)

Describe the development toolchain that you would like to select for beta and why.

*Docker (provides containers allowing independent microservices to be created and deployed) *Puppet (configuration management tool for Skyscape hosted servers) *Jenkins (open source tool used for continuous integration and deployment)