- Artykuły z tagiem distributed systems

Czy Twoja aplikacja na pewno będzie ostatecznie spójna ?

Dziel się z innymi:
Czy Twoja aplikacja na pewno będzie ostatecznie spójna ?

Architektura 238 dni, 19 godzin, 8 minut temu Daniel Dziubecki 185 źrodło rozwiń

What does maximum-connections, CPU autoscaling, money and distributed systems have in common? Find out by solving a task: how many servers should you get to run your service, given that maximum allowed average CPU usage can be 80%. Edit it on With increasing number of hosts in a fleet, the CPU utilization should be successively smaller. The proportion and exact curve will be different for each sy...

Dziel się z innymi:
How to estimate host fleet size? Why keeping CPU at 30% might NOT be waste of money?

Architektura 405 dni, 18 godzin, 34 minuty temu pwest 32 źrodło rozwiń

Let start right off the bat with quick overview what etcd is:distributed key/value store with failover mechanismheavily uses disk but also use in memory cacheAP regarding CAP theoremsequential consistency ( the strongest consistency guarantee availa...

Dziel się z innymi:
Service discovery with etcd -

Architektura 638 dni, 10 godzin, 36 minut temu undernotic 49 źrodło rozwiń

There are certain classes of exciting problems which are surfaced only in a massively distributed systems. This post will be about one of them. It's rare, it's real and if it happens, it will take your system down. The root cause, however, is easy to overlook.

[EN] The nightmare of large distributed systems

Architektura 826 dni, 21 godzin, 23 minuty temu http://dynamicallyinvokable... 74 źrodło rozwiń

One of the concepts of actor model that could be hard to grasp at the begining is fact that we will not operate on direct reference to actor instance. This can be a bit confusing before you’ll get used to it but by not using any direct references you’re sure to achieve very good level of encapsulation.

Dziel się z innymi:
Akka.NET #3: Actor selections, paths and references – where should you send your messages – Hryniewski.NET

Daj się poznać 2017 920 dni, 20 godzin, 57 minut temu Rafał Hryniewski 44 źrodło rozwiń

In previous post I’ve explained briefly what actor model is and why it’s so fun. Today we’ll create our ActorSystem instance, learn what it is and send first messages to them. I hope it will be nice and easy start.

Dziel się z innymi:
Akka.NET #1 – Creating Actor System and making first contact – Hryniewski.NET

Daj się poznać 2017 936 dni, 12 godzin, 19 minut temu Rafał Hryniewski 27 źrodło rozwiń

Actor model concept fascinated me since I’ve heard about it for the first time. It’s been on my todo list ever since and Get Noticed 2017 is great opportunity to give it a try. That’s why there is an actor responsible for almost anything in Me2.0. But, what is an actor, actor model and are benefits of using it in our projects? You’ll find out in a minute.

Dziel się z innymi:
Akka.NET #0 – Actor Model Basics – Hryniewski.NET

Daj się poznać 2017 937 dni, 18 godzin, 12 minut temu Rafał Hryniewski 133 źrodło rozwiń

Selected Aspects of Document Synchronization in Distributed Systems Two of the projects in which I have participated recently, were distributed systems based on the document replication. Each of them was slightly different, which affected the solutions. In this article I’m going to present briefly the main assumptions and requirements for each of the projects, as well as the implemented solutions. I’m also going to mention a few important problems that we had to deal with.General description of ...

[EN] Selected Aspects of File Synchronization in Distributed Systems | Technical blog

Bazy danych i XML 1976 dni, 18 godzin, 13 minut temu FutureProcessing 64 źrodło rozwiń

Simon: Jak część z Was pamięta, jakiś czas temu dosyć aktywnie blogowałem na temat szyny (tu, tu oraz tu). Od tej pory upłynęło już sporo czasu. Chciałoby się powiedzieć: "dziś sam jestem dziadkiem". Ale nie, wertersów Wam nie dam. Opowiem za to o moim dojrzewaniu do komunikacji za pomocą asynchronicznej wymiany komunikatów.

Simon says... : Historia pewnej szyny - epilog

Programowanie rozproszone 3776 dni, 3 godziny, 26 minut temu macko 108 źrodło rozwiń

Sklep z gadzetami
Dotnetos Conference


(32 891,59)
(32 816,53)
(27 178,29)
(21 178,88)
(20 336,33)
(13 018,14)
(10 510,13)
(9 775,28)
(8 358,27)
(6 822,96)
(6 214,22)
(5 393,84)
(4 097,38)
(4 004,63)
(3 863,06)
(3 599,49)
(3 448,35)
(3 318,39)
(3 224,66)
(3 105,41)