[Links of the Day] 17/05/2018 : Edge Computing and the Red Wedding problem, Vector Embedding utility , Scalability efficiency

• Towards a Solution to the Red Wedding Problem : interesting look at how to handle massive Read spike while being able to update (write spike ) the content at the same time. The authors propose to leverage edge computing to spread and limit the impact of a write-heavy spike in such network
• Magnitude : this is a really cool project for those out there dabbling with NLP and vector embedding. This package delivers a fast, efficient universal vector embedding utility.
• Scalability! But at what COST? : the authors of this paper introduce the concept of measuring the scalability performance of a solution by comparing it to the hardware configuration required before the platform outperforms a competent single-threaded implementation. As always, and often, most system and company do not need a monstrous cluster to satisfy their need. But it's always more glamorous to say: "we used a cluster" rather than: "I upgraded the RAM so the model can fit in memory".

[Links of the Day] 25/07/2017 : Universal Scalability Law Model , k8s + cloud native apps, python distributed execution engine

• usl4j : Implementation of Universal Scalability Law model, this is really cool because it allows you to model ( and predict ) when your system performance will start to degrade as its scale. It allows you to take real measurements from a live system and continuously build models. [github]
• daft : a tool for developers to create cloud-native applications on Kubernetes.
• ray : distributed execution engine written in python. Useful if you want to execute and schedule task across a cluster of nodes.

[Links of the Day] 01/09/2016 : Cloud reference model, Scaling with Threads and economyics of response time

• Economic Value of Rapid Response Time : classic 1989 paper demonstrating that lower software response time yield significant economic benefit with 
• ClouNS : A Cloud-native Application Reference Model for Enterprise Architects. The authors propose a reference model for cloud-native applications that relies only on a small subset of well standardized IaaS services. The reference model can be used for codifying cloud technologies. It can guide technology identification, classification, adoption, research and development processes for cloud-native application and for vendor lock-in aware enterprise architecture engineering methodologies.
• Scaling to Thousands of Threads : excellent blog post looking at the misconception that thread based system are inherently flawed when it comes to availability. 

Links of the day 08/12/2015 : CIA corporate sabotage manual, Cloud scalability patterns and 3D Ram technology

• CIA’s Simple Sabotage Field Manual : well... it seems to be the internal operations playbook for a lot of company out there
• Cloud Scalability Patterns : must watch for anybody moving applications to the cloud.
• 3D ram stacking : Interesting development in the 3d chip business and its far reaching consequence in memory. It seems that we are bridging the bandwidth gap with CPU however Latency and remain the majors roadblock.

Links of the day 13 - 02 - 2015

Today's links 13/02/2015: Scalable and resilience web site, CAP theorem, automated log analyzer and Exascale HPC challenges

• Scalable and Resilient website : lessons learned from all the biggest sites on the internet about how to build scalable and resilient architectures. 
• Perspectives on the CAP theorem : paper summary that show the CAP theorem in the broader context of a family of results in distributed computing theory that shows impossibility of guaranteeing both safety and liveness in an unreliable distributed system.
• Sequence: Automated Analyzer for Reducing 100,000's of Log Messages to 10's of Patterns
• Algorithmic and Software Challenges atExtreme Scales : presentation by Jack Dongarra  , quite redundant as the same theme are pretty common to all HPC exascale challenge : matrix operations optimizations, power, resilience, scalability, etc..

IBM Photonic 3D chip

Links of the day 23 - 01 - 2015

Today's links 23/01/2015: #cloud storage - Open vStorage, #bitcoin #blockchain scalability, shortest path in corporate communication

• Open vStorage :  its roadmap and some interesting bits on its architecture.
• Blockchain scalability : A look at the stumbling blocks to blockchain scalability and some high-level technical solutions.
• Surprising Facts About Shortest Paths : In a corporate communication network  the shortest path is not the fastest ( Social Network Analysis ). In other words, don’t let your train pass through the central hub for a shortcut, ’cause it’s going to stay there for a long long time.

Links of the day 21 - 01 - 2015

Today's links 21/01/2015: cost of #bigdata scalability and when you are stuck in the middle, to big for small data and to small for big data : #mediumdata

• Scalability! But at what COST? : Big data systems may scale well, but this can often be just because they introduce a lot of overhead. Rather than making your computation go faster, the systems introduce substantial overheads which can require large compute clusters just to bring under control. In many cases, you’d be better off running the same computation on your laptop. This has been a well know side effect in HPC as for certain type of problem high parallelism just create more overhead than accelerate the processing. The only need for such cluster is the lack of capabilities to buy hardware that is able to fit the necessary amount of data. I guess often people prefer to buy a lot of small cheaper server and say : "look i m running a cluster", than one single beefed up machine that would solve the problem faster.
• Medium Data : when your big data is too small to warrant a cluster but too big to fit within a single machine .. I think the authors of this article and the one above should collaborate on a follow up one. Also.. one size fit all does not exist.. News at ten.

Links of the day 05 - 11 -2014

Today's links 05/11/2014: #Docker and #LXD, scalability rule, Google #containers engine

• LXD : Shuttleworth announce LXD, a secure container technology design to address the isolation and security concern of exiting solution.
• Scalable commutativity rule : Whenever interface operations commute, they can be implemented in a way that scales
• Container engine: interesting that Google offer multiple container per VM management (1:M) while all its concurrent only offer a 1:1 mapping.