In a previous blog post we talked about how we use the programming language Go. But it only briefly touched on the issue of dependency management, where Go is reliant on backwards compatible or vendored software. This post is about …
This is cross posted from the 5th birthday celebration series on the GopherAcademy blog. When the UK Government Digital Service started working on GOV.UK, much of it was built in Ruby. Since then, we’ve used a number of different programming …
GOV.UK has used a Content Delivery Network (CDN) since its transition from beta to live in October 2012. When the contract with our first CDN provider came to an end in September 2013, we took advantage of what we'd learned …
As GOV.UK gets bigger, we often need to revisit the ways that we originally solved some problems. One thing that's changed recently is how we prepare for disaster recovery. Disaster Recovery The reality of working in technology is that software …
This is the fourth piece in a series of the router component we deployed in front of GOV.UK towards the end of 2013. You may also want to read the previous posts in the series. In developing the router, we …
Having created a comprehensive set of code tests for the Router (which we'll write about in this series soon) we were reasonably confident that it would do the right job in production. But "reasonably confident" isn't good enough; we wanted …
As you read in the previous post in this series, we have built a frontline router using Go. If you cast an eye across our many and varied open source projects, the common theme is that they're generally written in …
This is part one of what will be a series of blog posts about the new dynamic HTTP router that serves GOV.UK. This post describes our original motivations in building the router, and some of our experiences building the prototypes …