Taqsimlangan hisoblash xatolari - Wikipedia
Tarmoqli hisoblash xatolari nomi bilan ham tanilgan, xatoliklar tarqatilgan hisoblashlar haqidagi taxminlar (yoki eʼtiqodlar) roʻyxati boʻlib, bu dasturiy taʼminotni ishlab chiqishda nosozliklarga olib kelishi mumkin. Taxminlar quyidagilardan iborat:
- Tarmoq ishonchli
- Kechikish nolga teng
- Tarmoqli kengligi cheksizdir
- Tarmoq xavfsiz
- Topologiya o'zgarmaydi
- Bitta administrator bor
- Transport narxi nolga teng
- Tarmoq bir hil
Dastlabki to'rtta element Bill Joy va Tom Lyon tomonidan 1991 yilda ro'yxatga olingan va birinchi bo'lib Jeyms Gosling tomonidan "Tarmoqli hisoblash xatolari" sifatida tasniflangan. L. Peter Deutsch 5, 6 va 7-noto'g'rilarni qo'shib qo'ydi. 90-yillarning oxirida Gosling 8-chi xatoni qo'shdi.
Guruh o'sha paytda Sun Microsystems ichida sodir bo'layotgan voqealardan ilhomlangan.
Bardoshli kodni loyihalashda ushbu xatolarni diqqat bilan ko'rib chiqish kerak; Agar ushbu noto'g'ri tushunchalarning har biri tarqalgan tizimlarning haqiqatlari va murakkabliklari bilan shug'ullana olmaydigan noto'g'ri mantiqqa olib kelishi mumkin.
Shuningdek qarang: Taqsimllangan hisoblash xatolarini qidirish (1-qism) - Vaidehi Joshi Medium
The Fallacies of Distributed Computing on Wikipedia
Also known as Fallacies of Networked Computing, the Fallacies are a list of conjectures (or beliefs) about distributed computing, which can lead to failures in software development. The assumptions are:
- The network is reliable
- Latency is zero
- Bandwidth is infinite
- The network is secure
- Topology doesn't change
- There is one administrator
- Transport cost is zero
- The network is homogeneous
The first four items were listed by Bill Joy and Tom Lyon around 1991 and first classified by James Gosling as the "Fallacies of Networked Computing". L. Peter Deutsch added the 5th, 6th and 7th fallacies. In the late 90's Gosling added the 8th fallacy.
The group was inspired by what was happening at the time inside Sun Microsystems.
These fallacies should be considered carefully when designing code which is resilient; assuming any of these fallacies can lead to flawed logic which fails to deal with the realities and complexities of distributed systems.
See also:
O'zbekcha
English