The GOV.UK Verify team has changed the way its frontend is deployed. We take a deep dive into the technical challenges and how the load balancing changes give users a better experience.
William Palmer, GDS Lead Developer
The standards that underpin GOV.UK Verify have always been open but we started coding as a private project. Here’s a recap of our journey to coding in the open.
At GOV.UK Verify we take users’ security very seriously. Online security is constantly changing, and we need to be up to date at all times. We regularly update the service’s frontend to ensure it’s running the most secure and recent …
Related content and links
Technology in government
This is for everyone: documenting how we're building, assembling and running digital and technology projects across the UK government. Find out more.
Work with us
If you’re interested in jobs in this field, check out all open opportunities on the GDS careers site.
Find out more
- A new standard of testing for GOV.UK 8 October 2021
- What I learned when I moved from content design to technical writing 30 July 2021
- Automatically creating and rotating GOV.UK application secrets 23 July 2021