DISTRIBUTED COMPUTING

Glassbeam for Glassbeam (Part 4) - Helping Smart Engineering Teams be Smarter

In this post, let me explain how Glassbeam’s engineering team uses the Glassbeam Analytics solution to be an effective and responsive team to every bug and the not-so-nice user experiences that our customers could potentially face.

Here are some guidelines that our Engineering team uses to seek answers from log data-driven Glassbeam Analytics:

Geting the most out of akka clusters

Anyone serious about distributed systems or building one, commonly encounters issues such as replication, consistency, availability and partition tolerance (CAP) [1]. In a real life scenario, partition tolerance is inevitable. So the system must be able to handle partition tolerance when there are network outages. Therefore, ‘P’ in the CAP is a must for any distributed system. This has been backed by Peter Deutsch in his (EIGHT FALLACIES OF DISTRIBUTED COMPUTING).