This post outlines a recent production issue on the Platform as a Service for government (PaaS) and how it was resolved.
Platform as a Service for government
We’re building Government Platform as a Service (Gov PaaS) to host a range of services so teams across government don’t have to build their own hosting stack. This will make it easier and cheaper for teams across government to host applications, services and platforms.
This is the second guest post from Matthew Ford, the Technical Director of Bit Zesty, on the migration of the GOV.UK Trade Tariff service to the Platform as a Service for government (PaaS). Here Matthew writes about the technical lessons learned and how the Bit Zesty and PaaS teams resolved them.
We’re building a Platform as a Service, which will be used to host services from across GDS, and the rest of government. And, we’re looking for a senior product manager to help make this happen.
In July, the Trade Tariff became the first service to migrate to the Platform as a Service for government. In this post Matt Ford shares some of the benefits and challenges of the migration.
This post is about an incident on the 'Platform as a Service for government' production environment for hosting applications.
We’re keen to spread the hosting and platform message, so we travelled to Swansea Tech Hub. This was an ideal opportunity for us to reach out to 60 people working in agencies across the south west including Met Office, Driver and Vehicle Standards Agency, Intellectual Property Office, Office of National Statistics, and Companies House.
Last time we blogged we talked a bit about building a platform to host digital services, and we told you about how we chose cloud foundry. Before we move on to what we are up to now, here is a quick reminder of what we are doing and why.
Technical architect, Anna Shipman, explains the reasons for choosing Cloud Foundry as the technology for Platform as a Service.