Showing posts with label rump kernel. Show all posts
Showing posts with label rump kernel. Show all posts

Monday, August 10, 2015

Links of the day 10/08/2015 : Cryptocurrency architecture, Distributed data stream processing and Rump kernels

  • Architecture Of A Cryptocurrency : good overview of what make a cryptocurrency and the five pillars of its architecture : Network consensus, transaction Protocol and internal state
  • High-throughput, low-latency, and exactly-once stream processing with Apache Flink : on the evolution of fault-tolerant streaming architectures and their performance
  • On rump kernels and the Rumprun unikernel : a very good overview of the rump kernel . As stated, One of the key advantage of this type of unikernel is that it can run unmodified "legacy" applications. By that I means you can use your tested, running application that wasn't design for unikernel and slap it on top of rump. To a certain extend it allow a easy and smooth transition without the pain of re-coding everything from scratch. 

Monday, May 25, 2015

Links of the day 25 - 05 - 2015

Today's links 25/05/2015 : PIP for #GO, #RumpKernel stack and #Bitcoin discussion

Tuesday, April 28, 2015

Links of the day 28 - 04 - 2015

Today's links 28/04/2015: #Rump Kernel Stack, Disque Distributed In Memory MQ, #FusionIO new PCIe product, Power level estimation of VM systems
  • Ramp Stack : Nginx, MySQL, and PHP built on Rump Kernels without rearchitecting the application. Most of the work requires the app to be cross compile correctly (Nginx & MySQL). This implies that Unikernel-compatible unmodified POSIX C and C++ applications “just work” on top of Rump Kernels, provided that they can be cross- compiled.
  • Disque :a distributed, in memory, message broker by Redis folk. Not production ready but a promising start.
  • Pcie Flash : fusion IO is still kicking and deliver an interesting solution: up to 350,000 I/O operations per second (IOPS) on random reads and 385,000 IOPS on random writes (on the 3.2 TB model) with a 15k nanosecond write latency and 2.8 GB/sec of read bandwidth. .. However I still don't get why they don't want to use NVMe tech
  • Process-level Power Estimation in VM-based Systems : the authors describe a fine-grained monitoring middleware providing real-time and accurate power estimation of software processes running at any level of virtualization in a system.