Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

A PaaS for government

1,621 views

Published on

Slides from my Velocity EU keynote: http://velocityconf.com/devops-web-performance-eu-2015/public/schedule/detail/46814

Published in: Technology
  • Be the first to comment

A PaaS for government

  1. 1. Anna Shipman Technical Architect Government Digital Service @annashipman
  2. 2. The Government Digital Service
  3. 3. We are a unit of government within the UK’s Cabinet Office GDS@annashipman
  4. 4. GDS@annashipman We started with GOV.UK
  5. 5. GDS@annashipman The best place to find government services and information
  6. 6. We’re not just fixing websites GDS@annashipman
  7. 7. We also work with departments to transform digital services GDS@annashipman
  8. 8. GDS@annashipman
  9. 9. GDS@annashipman
  10. 10. There are over 800 services GDS@annashipman
  11. 11. We need to look at the common problems GDS@annashipman
  12. 12. And the most common problem is hosting GDS@annashipman
  13. 13. Platform as a Service
  14. 14. I probably don’t need to explain PaaS to you GDS@annashipman
  15. 15. Here is the slide we’re using to explain the idea in government GDS@annashipman
  16. 16. GDS@annashipman
  17. 17. This detracts from the time teams can spend on their main expertise GDS@annashipman
  18. 18. GDS@annashipman
  19. 19. Additional thing for government: procurement is hard GDS@annashipman
  20. 20. Our initial thoughts
  21. 21. Self-service GDS@annashipman
  22. 22. Self-service So infrastructure team don’t just do admin GDS@annashipman
  23. 23. Support model GDS@annashipman
  24. 24. Support model App developers on-call for their apps GDS@annashipman
  25. 25. Support model App developers on-call for their apps Platform team on-call for platform GDS@annashipman
  26. 26. Support model App developers on-call for their apps Platform team on-call for platform No runbooks GDS@annashipman
  27. 27. Support model App developers on-call for their apps Platform team on-call for platform No runbooks Better experience for the end-user GDS@annashipman
  28. 28. Multi-tenancy GDS@annashipman
  29. 29. Multi-tenancy Granularity of user permissions GDS@annashipman
  30. 30. Multi-tenancy Granularity of user permissions Handling resource contention GDS@annashipman
  31. 31. Multi-tenancy Granularity of user permissions Handling resource contention Isolation from other tenants GDS@annashipman
  32. 32. Multiple cloud providers GDS@annashipman
  33. 33. Multiple cloud providers To avoid vendor lock-in GDS@annashipman
  34. 34. Multiple cloud providers To avoid vendor lock-in Difficult to add later GDS@annashipman
  35. 35. Multiple cloud providers To avoid vendor lock-in Difficult to add later Details of how unclear at this stage hot/hot? hot/warm? GDS@annashipman
  36. 36. What we’ve done
  37. 37. GDS@annashipman
  38. 38. GDS@annashipman
  39. 39. GDS@annashipman
  40. 40. GDS@annashipman
  41. 41. GDS@annashipman
  42. 42. We decided to use Tsuru for the initial prototype GDS@annashipman
  43. 43. Showed it to users in government to get feedback GDS@annashipman
  44. 44. Meanwhile building same functionality in Cloud Foundry to compare GDS@annashipman
  45. 45. We haven’t worked out which is most suitable for us yet GDS@annashipman
  46. 46. GDS@annashipman
  47. 47. That’s not what I want to talk about now GDS@annashipman
  48. 48. Though if these are problems that interest you, we are hiring! https://gds.blog.gov.uk/jobs/@annashipman
  49. 49. What we’ve learned from users
  50. 50. They definitely like the idea of a PaaS GDS@annashipman
  51. 51. Self-service is good for both sides GDS@annashipman
  52. 52. Multi-tenancy is important GDS@annashipman
  53. 53. Support model had buy-in GDS@annashipman
  54. 54. But the feedback from users on multiple cloud providers was not what we expected GDS@annashipman
  55. 55. None of our users wanted it GDS@annashipman
  56. 56. And it’s very hard GDS@annashipman
  57. 57. Lowest common denominator GDS@annashipman
  58. 58. Google Compute Engine doesn’t have internal load balancers GDS@annashipman
  59. 59. Can’t take advantage of cool features of all the providers GDS@annashipman
  60. 60. We were conflating resilience with commercial concerns GDS@annashipman
  61. 61. Users still have a need to avoid being locked in to one vendor GDS@annashipman
  62. 62. We are now looking at other ways to address that GDS@annashipman
  63. 63. What we’ve learned about PaaS
  64. 64. I no longer think we just need to sit tight for two years GDS@annashipman
  65. 65. Fast growing field but it’s diversifying GDS@annashipman
  66. 66. For example, virtualisation vs hardware GDS@annashipman
  67. 67. Only some will support multi-tenancy GDS@annashipman
  68. 68. And we now know multi-tenancy is important to our users GDS@annashipman
  69. 69. GDS@annashipman@annashipman https://www.gov.uk/design-principles
  70. 70. The most important thing...
  71. 71. Make sure you understand what your users need GDS@annashipman
  72. 72. Thanks! Anna Shipman @annashipman

×