The FT healthcheck standard
GET http://{service}/__health
Slide 74
Slide 74 text
The FT healthcheck standard
GET http://{service}/__health
returns 200 if the service can run the healthcheck
Slide 75
Slide 75 text
The FT healthcheck standard
GET http://{service}/__health
returns 200 if the service can run the healthcheck
each check will return "ok": true or "ok": false
Slide 76
Slide 76 text
No content
Slide 77
Slide 77 text
No content
Slide 78
Slide 78 text
@sarahjwells
Healthchecks are unit tested
Slide 79
Slide 79 text
@sarahjwells
Keeping information near to the code
Slide 80
Slide 80 text
@sarahjwells
Update automatically on deploy
Slide 81
Slide 81 text
@sarahjwells
Other teams need to adapt too
Slide 82
Slide 82 text
@sarahjwells
Change and release management
Slide 83
Slide 83 text
@sarahjwells
2256 releases = 53 working days doing CRs
Slide 84
Slide 84 text
@sarahjwells
Automation, again
Slide 85
Slide 85 text
No content
Slide 86
Slide 86 text
No content
Slide 87
Slide 87 text
@sarahjwells
Github web hook for our CRs
Slide 88
Slide 88 text
No content
Slide 89
Slide 89 text
@sarahjwells
First line support
Slide 90
Slide 90 text
@sarahjwells
There are many different technologies for them to
understand now
Slide 91
Slide 91 text
@sarahjwells
Our development teams don’t know the whole
system either…
Slide 92
Slide 92 text
No content
Slide 93
Slide 93 text
@sarahjwells
Operating microservices *is* a
challenge
Slide 94
Slide 94 text
@sarahjwells
The benefits can be worth it…
Slide 95
Slide 95 text
Deploys to production last year
Slide 96
Slide 96 text
Deploys to production of the monolith
Slide 97
Slide 97 text
@sarahjwells
But you have to be prepared to pay the cost