MPI was deisgned tightly-coupled compute clusters with fast, reliable networks. Spread and ØMQ are designed for large distributed systems. If you’re designing a parallel scientific application, go with MPI, but if you are designing a persistent distributed system that needs to be resilient to faults and network instability, use one of the others. MPI has … Read more
OK, let me start. A distributed logger with a high-precision global time axis – allowing to register events from different machines in a distributed system with high precision and independent on the clock offset and drift; with sufficient scalability to handle the load of several hundred machines and several thousand logging processes. Such a logger … Read more
I have never tried it, but what about redis ? Its homepage says (quoting) : Redis is a key-value database. It is similar to memcached but the dataset is not volatile, and values can be strings, exactly like in memcached, but also lists and sets with atomic operations to push/pop elements. In order to be … Read more
EJBs are built on top of RMI. Both imply Java clients and beans. If your clients need to be written in something else (e.g., .NET, PHP, etc.) go with web services or something else that speaks a platform-agnostic wire protocol, like HTTP or XML over HTTP or SOAP. If you choose RMI, you don’t need … Read more
NServiceBus is growing in popularity. It is open source as well. Here is a Hanselminutes episode with Scott Hanselman talking with Udi Dahan about NServiceBus to help grok it. You should definitely evaluate using it. UPDATE: There’s also a DNR TV episode which shows what it’s like to build an NServiceBus solution from scratch here: … Read more
When you upload something, the file is chunked by ipfs and stored in your cache folder (.ipfs). If you check the file existance on another peer of the network (say the main gateway, ipfs.io) that peer requests the file from you and caches it too. If later you switch off your daemon and you can … Read more
Ok, to understand it, one needs to understand several parts. In order to provide ordering total order, the message can be sent only to one consumer. Otherwise it would be extremely inefficient, because it would need to wait for all consumers to recieve the message before sending the next one: However, although the server hands … Read more
Free Software Projects Powered by ZooKeeper: AdroitLogic UltraESB Akka Eclipse Communication Framework Eclipse Gyrex GoldenOrb Juju Katta KeptCollections Mesos Neo4j Norbert Talend ESB redis_failover Apache Projects Powered by ZooKeeper: Apache Accumulo Apache BookKeeper Apache CXF DOSGi Apache Flume Apache Hadoop MapReduce Apache HBase Apache Hedwig Apache Kafka Apache S4 Apache Solr Source: https://cwiki.apache.org/confluence/display/ZOOKEEPER/PoweredBy
According to git push manual page: git push origin experimental Find a ref that matches experimental in the source repository (most likely, it would find refs/heads/experimental), and update the same ref (e.g. refs/heads/experimental) in origin repository with it. If experimental did not exist remotely, it would be created. This is the same as: git push … Read more