# Dealing With Murphy's Law at upday.

DevFeed: [Dealing With Murphy's Law at upday.](<https://devfeed.tech/articles/dealing-with-murphy-s-law-at-upday-35107.md>)

Original publisher: [Read original article](<https://upday.github.io/blog/dealing-with-murphy-s-law-at-upday/>)

Author: Nicola Miotto (nicola@upday.com)

Published: 2017-07-24T04:39:55Z

Content type: article

Language: en

Sources: [Upday](<https://devfeed.tech/sources/upday.md>)

Topics: [resiliency](<https://devfeed.tech/topics/resiliency.md>), [Android](<https://devfeed.tech/topics/android.md>), [App](<https://devfeed.tech/topics/app.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [samsung](<https://devfeed.tech/topics/samsung.md>), [User experience (UX)](<https://devfeed.tech/topics/ux.md>), [Users](<https://devfeed.tech/topics/users.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [backend](<https://devfeed.tech/tags/backend.md>), [behaviour](<https://devfeed.tech/tags/behaviour.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [devices](<https://devfeed.tech/tags/devices.md>), [errors](<https://devfeed.tech/tags/errors.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [outage](<https://devfeed.tech/tags/outage.md>), [resiliency](<https://devfeed.tech/tags/resiliency.md>), [samsung](<https://devfeed.tech/tags/samsung.md>), [service](<https://devfeed.tech/tags/service.md>), [settings](<https://devfeed.tech/tags/settings.md>)

## AI overview

The article discusses the architecture of upday's Android news app, focusing on resiliency and robustness around the personalized My News feature. It also explains the app's news streams and the service-level agreement severity levels used to respond to incidents.

## Source excerpt

In this blog post we will provide a few insights on the architecture of the upday news app (both backend and frontend), focusing on the work that has been put on the resiliency and robustness of the components around the My News feature. upday & Samsung Before digging into the technicalities, it's worth to spend a few words on what upday is and which responsabilities we have towards our stake holders. The App upday is a fruit of a collaboration between Axel Springer and Samsung. The end result is a news application for Android, pre-installed as the default news-app on most of the Samsung devices (S7, S8, A series etc). The one purpose of the application is to deliver relevant news content to the users. The goal is achieved by means of the two news streams that the app provides: Top News: this section is an editorial curated news stream, whose titles and headlines are manually crafted by a team of editors (in each of the available countries). It's supposed to provide the user with all the relevant news of the moment, independently from taste and preferences. My News: this is the "machine curated" news stream, generated by a swarm of super intelligent cyber beings enslaved to our will. Or at least that's how business sometimes likes to sell it. The important thing is that this stream is personalized based on the user explicit feedback and settings and behaviour. SLA With Samsung Collaborations with big players come always at a cost. For the engineering team at upday this cost is the Service Level Agreement that we need to commit to. So, when a problem with the service occurs, it's categorized in a specific severity level that also defines then the actions to take. These are, in Layman's terms, the 4 severity levels of our SLA: Severity 4: An Error affecting non- upday 's Services with little or no Users impact. More concisely: no one cares. It's hit once a single third-party picture wouldn't load, for instance. Severity 3: Errors that causes degradation of the UX. Lik