we move forward with it i would like to discuss for a brief moment why is reliability so important well if i'm being honest it's not that important um the reason for that is being reliable is not the first priority that most of startups have however i would mention that as your company grows it would really care about managing its reputation because think about a very big app like google photos if for example there is a newborn baby in a family and the parents they are capturing the snapshots and photos and they are uploading it to google photos app and uh they you know keep on clearing the photos from their phone to keep it you know uh like have enough storage for their phone to function efficiently so after three months or four months if they go back to the google photos app and if they are not able to see those photos or if those photos are corrupted on the back end of google then this would be really bad right so companies like google they would really invest a lot in being reliable because otherwise it's really bad experience and such companies they really do care about their users as well as the reputation the other thing is reliability is also important because if for example you are not reliable your backend is not reliable because of for example not doing better error handling or if you are having some bugs then the thing is if you are not capturing them towards the development side and it can be due to some reasons like lack of testing or you were not having testing as a priority because you had other deliveries in your mind so this can also affect your productivity because these things can stay dormant for a while and later on when they come up or when they fired up you realize that there is some bug you do the diagnosis at that point of time you have to do end-to-end diagnosis most of the times and then you figure out okay this is where the problem is and then you fix it and then you test or probably you release it to production if it was handled beforehand while you were in the development phase it could have saved a lot of time so that is why if you are if your system is reliable if it's doing a lot of things as is expected to it's well tested then it is also in the longer and it's more productive so having said that again as i'm saying it's always a trade-off and making systems reliable it of course needs development cost and sometimes you might have to sacrifice on that for example if you are developing a prototype or something like that all right now let's talk about fault versus failures so failure is something like entire system entire app is down and user is not able to get the service for which your app was meant to do however fault is basically um you can say something like if you are having NUMBER_TOKEN servers and one server died just because of something like probably it was running on some machine where hard disk got corrupted or probably there was an outage and but if you are having other servers if you are having eight or nine different servers then overall i i don't think there would be any impact and you can wait to turn that other server which went down you can turn it up again right so this is a very good reliable example in which you were having multiple servers to take care of such faults and you did not led faults to become a failure right if you were having only one server and if for example let's say the hard disk corrupted or probably there was power outage because of his your
NO_SEGMENT_TOKEN