Today I decided to think about Google's book "Engineering Reliable Mobile Applications" or as I call it for myself Mobile SRE Book, where SRE is site reliability engineering:)

Thanks to Google for popularizing SRE practices and a whole bunch of books on building reliable services.

The book, which I decided to recall today, came out about 3 years ago and very qualitatively highlighted the features of mobile applications that are important from the point of view of SRE:

1. Scale – the scale can be significant, devices are billions, and device models are thousands and it is not always clear what the problem is.
2. Control – control over native applications is very limited, because unlike server applications, we often cannot force the download of a new binary and do not control the device on which the applications are deployed.
3. Monitoring – with such variability, we should collect individual metrics, not combinations, of which there are too many. Plus, you need to take into account the side effects of logging in the form of traffic and battery consumption.
4. Change Management – unlike server side applications in the mobile world, we can not roll back, so you need to release carefully and only roll forward is possible. And then the book understands how to make mobile applications reliable taking into account these features.

A summary of the book can be read in my review https://bit.ly/mobileSREbook The full version of the book is available here. https://www.oreilly.com/library/view/engineering-reliable-mobile/9781492057444/

#SRE #Software #ExternalReview #Mobile #Processes