in ,

Checklist about Engineering Reliable Mobile Applications, Hacker News


Define business requirements (SLA / SLO / SLI) 1 – before development monitoring high Quantify, example, Availability SLI, Satisfying Latency SLI (Define your release train

1 – before development deployment Moderate Release Cycle, alpha, beta, polished, external, prod … Define timeouts / retries / circuit-breakers / fallback for every call 2 – during development Availability Moderate Set feature toggling / Gatekeeper 2 – during development security Use them according to the relevant distribution platform’s rules Record events 2 – dur ing development monitoring high (eg. action, location) Be immutable 2 – during development reliability high Write unit tests 2 – during development reliability high Monitoring battery / network usage 2 – during development monitoring (Medium) Define forward compatibility 2 – during development forward compatibility high Prevent app from crashing, being unavailable because of server API changes Set app versioning (2 – during development backward compatibility low Semantic versioning (https: / /semver.org/) Add caching 2 – during development availability Moderate (Add documentation 2 – during development (documenting high Support i (n) 2 – during development reliability Moderate Implement CI / CD 2 – during development deployment high Support prod / test mode switch 2 – during development reliability Moderate Be forward compatible 2 – during development availab ility high Considering the scale and lack of control in the mobile environment, managing changes in a safe and reliable manner is arguably one of the most critical pieces of managing a reliable mobile application. Crash / error tracing 3 – before production troubleshooting high Update changelog 3 – before production deployment low Consider risk / criticity 3 – before production

security

high ) Staged rollout / Phased Releases 3 – before production reliability ** (high Define a progressive release life cycle Runbook, configure alerting 3 – before production recoverability Moderate Dogfooding / Internal testing 3 – before production reliability high Test all rollback toggles / killswitch before deploying 3 – before production reliability high Be GDPR compliant 3 – before production security high If your app is available in Europe. Post-mortems 4 – after production monitoring low

Brave Browser
Read More
Payeer

What do you think?

Leave a Reply

Your email address will not be published.

GIPHY App Key not set. Please check settings

Dow Turns Positive Thanks to Monster 4% Rally In Boeing (BA) Stock, Crypto Coins News

Dow Turns Positive Thanks to Monster 4% Rally In Boeing (BA) Stock, Crypto Coins News

Damian Conway on multiple Raku ways to compute e, Hacker News