Interface vs Abstract Class
1.We implement one or more interfaces but we can only extend one class.Because java do not allow multiple inheritance.
2.while creating variables or methods inside Abstract Class we can use any acces modifiers, but in interface the variables are by default public final.
Since java 8, we can create default methods inside interface.
3.Abstract classes are faster than interfaces as interface need to search overridden methods.
1.We implement one or more interfaces but we can only extend one class.Because java do not allow multiple inheritance.
2.while creating variables or methods inside Abstract Class we can use any acces modifiers, but in interface the variables are by default public final.
Since java 8, we can create default methods inside interface.
3.Abstract classes are faster than interfaces as interface need to search overridden methods.
Let's talk about ACID (:
Atomicity - Either execution is complete or not, there is no partial execution.
Consistency - When you want to send $100 to your friend but you only have $40, in simple case after execution you end up having $-60 in your balance. According to the rule Consistency, in such case the transaction should not be executed, because you don't have enough money.
Isolation - Imagine a case where you send $100 to your friend and it takes some time to increase your friend's balance. In such cases, even though you send money, you should see the old balance that you had. Balance should be updated only when your friends get the money that you send.
Durability - You send $100 to your friend and see the check of successful execution and at that time the server shut downs. When you come back if you see you old balance it means The execution is not durable
Atomicity - Either execution is complete or not, there is no partial execution.
Consistency - When you want to send $100 to your friend but you only have $40, in simple case after execution you end up having $-60 in your balance. According to the rule Consistency, in such case the transaction should not be executed, because you don't have enough money.
Isolation - Imagine a case where you send $100 to your friend and it takes some time to increase your friend's balance. In such cases, even though you send money, you should see the old balance that you had. Balance should be updated only when your friends get the money that you send.
Durability - You send $100 to your friend and see the check of successful execution and at that time the server shut downs. When you come back if you see you old balance it means The execution is not durable
Forwarded from Otabek’s I/O
CTE - endi easy
Ushbu maqolani o'qib chiqish orqli CTE haqida o'rganib, practice qilib chiqishingiz mumkin.
Yana o'sha gap: Ma'qolani o'qish tekin 🙂
Bundan keyingi mavzular advanced topikda qilishga qaror qildim chunki tutorial yozish unchalik ham yoqmadi
.
.
.
Ushbu maqolani o'qib chiqish orqli CTE haqida o'rganib, practice qilib chiqishingiz mumkin.
Yana o'sha gap: Ma'qolani o'qish tekin 🙂
Bundan keyingi mavzular advanced topikda qilishga qaror qildim chunki tutorial yozish unchalik ham yoqmadi
.
.
.
Medium
CTE - endi easy
Common Table Expression (CTE) — SQLni kuchli va eng zo’r xususiyatlaridan biri xisoblanadi. Bunday deyishimga sabab bilamizki dasturlash…
Forwarded from Otabek’s I/O
Backendga sayohat
Bismillah! Aytilgan gap otilgan o'q.
Vaqt muammo bo'lib ba'zan to'xtab qolsak ham bizni tark etmaysiz degan umiddamiz.
Qo'ldan kelgancha tushunchalarni sodda, jaydari va vizuallashtirishga urunayabmiz.
Postni foydali deb topgan bo'lsangiz ulashib qo'ying, sizdan faqat bitta click ketadi.
Post haqida feedback qoldirib ketsangiz, uni yaxshilashga yordam qilgan bo'lardingiz.
@unotech_log
Bismillah! Aytilgan gap otilgan o'q.
Vaqt muammo bo'lib ba'zan to'xtab qolsak ham bizni tark etmaysiz degan umiddamiz.
Qo'ldan kelgancha tushunchalarni sodda, jaydari va vizuallashtirishga urunayabmiz.
Postni foydali deb topgan bo'lsangiz ulashib qo'ying, sizdan faqat bitta click ketadi.
Post haqida feedback qoldirib ketsangiz, uni yaxshilashga yordam qilgan bo'lardingiz.
@unotech_log
Telegraph
Backendga sayohat
Ushbu loyiha sizni Backend soxasiga biroz bo'lsada olib kirish yoki bilmaganlaringizni sizga qaysidir darajada o'rgatish maqsadida yozilayabdi. Bunda olgan bilimlaringizni boshqalar bilan ham bo'lishib borishni va bu jarayonda bizni ham eslab o'tishni unutmasangiz…
Forwarded from Vohid Karimov (Vohid Karimov)
Blameless culture
yohud barmoq bilan ko'rsatmaymiz!
Men ishlagan kompaniyalarni ko'pida blameless culture bo'lgan ekan — omadli bolamanda 😉
Birinchi bo'lib blameless culture'ni Shved kompaniyasi bilan ishlayotganimda ko'rganman. "Database o'chib ketdi" degan yangilikga Shvedsiyalik managerimizni reaksiyasi "How can we recover it?" va recover qilib bo'lganimizdan keyin "What did we learn from it?" bo'lgandi.
"Iye, shunaqa qilsa ham bo'larkanda?" degandim o'zimga o'zim og'zim ochilib 😲
Umuman olganda blameless culture nega to'g'ri yondashuv?
— bo'ladigan ish bo'ldi, aybdorni topib uni ayblashdan foyda yo'q
— aybdor shundoq ham qovun tushurib qo'yganini sizni yordamingizsiz ham biladi
— blameless culture ishchilar orasida xotirjamlikni tiklaydi va ular risk/ma'suliyat olishdan qo'rqishmaydi
— odamgarchilik, duh!
Siz oddiy ishchimisiz? Yaxshi, blameless culture'ni o'zingizdan boshlang. Odamlar siz bilan ishlashni xoxlab qolishadi 🙂
Siz team lead yoki managermisiz? Undanda yaxshi, siz ham "Bundan nimani o'rgandik?" kabi savollarni so'rab komandada blameless culture'ni yo'lga qo'ying. Sizni komandangizda hamma ishlashni xoxlab qolishadi 🙂
Siz kompaniya boshlig'imisiz? Yanada yaxshi, blameless culture'ni rag'batlantiradigan team lead va managerlarni ishga oling. Sizni kompaniyangizda hamma ishlashni xoxlab qoladi 🙂
yohud barmoq bilan ko'rsatmaymiz!
Men ishlagan kompaniyalarni ko'pida blameless culture bo'lgan ekan — omadli bolamanda 😉
Birinchi bo'lib blameless culture'ni Shved kompaniyasi bilan ishlayotganimda ko'rganman. "Database o'chib ketdi" degan yangilikga Shvedsiyalik managerimizni reaksiyasi "How can we recover it?" va recover qilib bo'lganimizdan keyin "What did we learn from it?" bo'lgandi.
"Iye, shunaqa qilsa ham bo'larkanda?" degandim o'zimga o'zim og'zim ochilib 😲
Umuman olganda blameless culture nega to'g'ri yondashuv?
— bo'ladigan ish bo'ldi, aybdorni topib uni ayblashdan foyda yo'q
— aybdor shundoq ham qovun tushurib qo'yganini sizni yordamingizsiz ham biladi
— blameless culture ishchilar orasida xotirjamlikni tiklaydi va ular risk/ma'suliyat olishdan qo'rqishmaydi
— odamgarchilik, duh!
Siz oddiy ishchimisiz? Yaxshi, blameless culture'ni o'zingizdan boshlang. Odamlar siz bilan ishlashni xoxlab qolishadi 🙂
Siz team lead yoki managermisiz? Undanda yaxshi, siz ham "Bundan nimani o'rgandik?" kabi savollarni so'rab komandada blameless culture'ni yo'lga qo'ying. Sizni komandangizda hamma ishlashni xoxlab qolishadi 🙂
Siz kompaniya boshlig'imisiz? Yanada yaxshi, blameless culture'ni rag'batlantiradigan team lead va managerlarni ishga oling. Sizni kompaniyangizda hamma ishlashni xoxlab qoladi 🙂