Verinin temsili, ilenmesi, saklanmas脹nda gelien ve deien
koullar ele al脹nd脹ktan sonra, b端y端k verinin ilenmesi konusu
ele al脹n脹yor.
Verinin anlamland脹r脹lmas脹 konusunda deien terimler, 端nvanlar, algoritmalar, kullan脹lan aletler konusunda deerlendirmeler payla脹ld脹.
sunumun videosuna aa脹daki adresten ulaabilirsiniz.
https://www.youtube.com/watch?v=pnvvMU8L-O0
This document provides an overview of event-driven architecture and distributed transactions with microservices. It discusses event-driven programming and what constitutes a distributed transaction when using microservices. It then covers some common solutions for distributed transactions like the 2PC and Saga patterns. The Saga pattern uses a choreography or orchestration approach and events to coordinate transactions across services. Message brokers like Kafka, RabbitMQ and Azure Event Hub are discussed for facilitating event-driven architectures. Vert.x and Spring WebFlux are presented as reactive frameworks that are non-blocking and scale well.
JavaScript was originally created in 10 days in 1995 by Brendan Eich for Netscape Navigator under the name Mocha and later renamed LiveScript before being officially called JavaScript. It was standardized by ECMA International as ECMAScript, with JavaScript being the most common implementation. Over time, JavaScript has evolved through various versions of ECMAScript and community efforts, and is now used for both browser and server-side applications with modern frameworks and tools that simplify development.
Verinin temsili, ilenmesi, saklanmas脹nda gelien ve deien
koullar ele al脹nd脹ktan sonra, b端y端k verinin ilenmesi konusu
ele al脹n脹yor.
Verinin anlamland脹r脹lmas脹 konusunda deien terimler, 端nvanlar, algoritmalar, kullan脹lan aletler konusunda deerlendirmeler payla脹ld脹.
sunumun videosuna aa脹daki adresten ulaabilirsiniz.
https://www.youtube.com/watch?v=pnvvMU8L-O0
This document provides an overview of event-driven architecture and distributed transactions with microservices. It discusses event-driven programming and what constitutes a distributed transaction when using microservices. It then covers some common solutions for distributed transactions like the 2PC and Saga patterns. The Saga pattern uses a choreography or orchestration approach and events to coordinate transactions across services. Message brokers like Kafka, RabbitMQ and Azure Event Hub are discussed for facilitating event-driven architectures. Vert.x and Spring WebFlux are presented as reactive frameworks that are non-blocking and scale well.
JavaScript was originally created in 10 days in 1995 by Brendan Eich for Netscape Navigator under the name Mocha and later renamed LiveScript before being officially called JavaScript. It was standardized by ECMA International as ECMAScript, with JavaScript being the most common implementation. Over time, JavaScript has evolved through various versions of ECMAScript and community efforts, and is now used for both browser and server-side applications with modern frameworks and tools that simplify development.
Online Dashboard, art脹k dashboard tasar脹m脹, g旦sterimi ve yetkilendirme i巽in ekstra ara巽 almaya gerek kalmaks脹z脹n herhangi bir servisle entegre olarak istediiniz zaman g端ncel dashboardu anl脹k olarak istediiniz platformda g旦r端nt端lemeye olanak sunan bir u巽tan uca 巽旦z端md端r.
SoBot Sistek 巽at脹s脹 alt脹nda bulunan t端m projelerle kolayca entegre olabilecek, m端terilerin destek elamanlar脹na ihtiyac脹ndan dolay脹 ortaya 巽脹km脹 bir ChatBot uygulamas脹d脹r.
This document discusses and compares several popular hybrid mobile application development frameworks: Ionic, React Native, and Flutter. It outlines some key advantages like reduced development time and shared codebases across platforms. It also notes potential disadvantages like performance issues and instability compared to purely native development. Example platforms, technologies, and common problems for each framework are described.
2. Not Only SQL
RDBMSe alternatif olarak ortaya 巽脹kan, aslen internetin g端n ge巽tik巽e artan
verisini depolayabilmek ve y端ksek trafie sahip sistemlerin ihtiya巽lar脹na cevap
verebilmek amac脹yla ortaya 巽脹km脹 yatay olarak 旦l巽eklendirilebilen sistemlere
denir.
RDBMSler ilem (transaction) tabanl脹 巽al脹an sistemlerdir. Bu ilemlerin stabil
巽al脹mas脹 ve veri b端t端nl端端 i巽in ACID (Atomicity, Consistency, Isolation,
Durability) kurallar脹 bulunur. NoSQL sistemleri bu kurallar脹n tamam脹na uymaz.
4. Okuma yazma performans脹 olarak RDBMSlerden daha performansl脹 olabilirler.
Yatay olarak geniletilebilirler
Binlerce sunucu bir arada k端me olarak 巽al脹abilir ve 巽ok b端y端k veri 端zerinde
ilem yapabilirler.
Esnek yap脹
ou a巽脹k kaynak ve 端cretsiz, ucuz maliyet
5. RDBMSde yap脹lan uygulamalar脹n NoSql sistemlerine ta脹nmas脹 zahmetlidir.
Transaction kavram脹 bulunmad脹脹ndan veri kayb脹 s旦z konusu olabilir.
Veri g端venlii konusunda RDBMS kadar gelimi deildir.
Dok端man ve profesyonel destek konusundan eksiklikleri olabilir.
7. MongoDB, dok端man tabanl脹, C++ ile gelitirilen bir NoSql veritaban脹d脹r. Veriler
BinaryJson(BSON) t端r端nde dok端manlarda tutulur.
MongoDBnin en 旦nemli 旦zellii, ilikisel modeli (relational model)
kullanmamas脹d脹r.
Tablo yoktur, tasar脹m yoktur, iliki yoktur.
Cross-platformdur
A巽脹k kaynak kodlu
Dinamik veri yap脹s脹
H脹zl脹 okuma ve yazma
B端y端k veri ile 巽al脹abilme
8. Belgeye dayal脹 modelde, ilikisel modelin sat脹r (row) kavram脹 yerine, 巽ok daha
esnek bir yap脹 olan belge (document) kavram脹 kullan脹lmaktad脹r. G旦m端l端
belgelere (embedded documents) ve dizilere (arrays) m端saade edilmesi ile, 巽ok
karma脹k hiyerarik yap脹lar脹 tek bir kay脹t (record) i巽inde saklamak olanakl脹 hale
gelmitir.
Join yok!!
Transaction yok!!
11. Buna 旦rnek olarak bir 端r端n ve bu 端r端ne ait yedek par巽alar verebiliriz.Burada
par巽alar 巽ok fazla bilgisi olaca脹 ve par巽alar脹n deikenlikleri yani updatelerinin
de 巽ok olaca脹n脹 d端端nerek relational databaselerdeki gibi 端r端nde par巽alar脹n
idlerini tutup programlama an脹nda gerekli datalar脹 巽ekip birletirme yapabiliriz.
12. {
name : product A,
manufacturer : ABC Company,
catalog_number: 1234,
parts : [
ObjectID(AAAA),
ObjectID(F17C),
ObjectID(D2AA),
]
}
13. {
name : product A,
manufacturer : ABC Company,
catalog_number: 1234,
parts : [
{ id : ObjectID(AAAA), name : Par巽a1},
{ id: ObjectID(F17C), name : Par巽a2 },
{ id: ObjectID(D2AA), name : Par巽a3 }
]
}
Burada 端r端n端 g旦sterceimiz sayfada tek bir nesneyi 巽ekerek 端r端ne ait yedek par巽a adlar脹n脹 da
listeyebiliriz
14. Denormalize yap脹larar脹 b端y端k update maliyetleri yoksa tercih
etmeliyiz.Yukar脹daki 旦rnekte olduu gibi yedek par巽a isimleri 巽ok fazla
deimeyeceini var say脹yoruz.
Balant脹l脹 kay脹t say脹s脹 azsa ve bunlarda baka yerde kullanmayacaksa i巽 i巽e
dok端man yap脹s脹nda saklayabiliyoruz.rnek kiiye ait adresler
Eer nesneye tek ba脹na s端rekli eriim ihtiyac脹 varsa embedded ekilde
kullanmamaya 巽al脹脹n
16. Bloglar (Post, Comment, Like)
ye Bilgileri (Kullanici > Kullanici Detaylar脹)
Log datas脹 saklamak
Corafi bilgi saklamak
Zaman i巽inde yap脹s脹 deiecek uygulamalar
Big data projeleri
oklu sunucu gerektirebilecek da脹t脹k projeler