Profile picture Marc Andreu
Abastract squared tiles with colored shapes on top of each tile.

9 Side notes JAX London 2016

Quick notes from session 9 of JAX London 2016. Four Distributed Systems Reference Architectures preseneted by Tim Berglund.

· Q.Assistance · 1 minutes·

Overview

Session: 12th Oct — 12:00 to 12:50 Four Distributed Systems Reference Architectures by Tim Berglund, DataStax

Notes

  • Presentation slides.
  • Distributed systems characteristics:
    • The computers operate concurrently
    • The computers fail independently
    • The computers do not share a global clock
  • Sharding the architecture is ok, but sharding the DB is KO
  • Bounded (batch) vs Unbounded (streaming)
  • Streaming architectures:
    • Apache Beam: Apache Beam is an open source, a unified programming model that you can use to create a data processing pipeline.
    • Apache Flink: Flink’s core is a streaming data flow engine that provides data distribution, communication, and fault tolerance for distributed computations over data streams.
    • Apache Storm: Apache Storm is a free and open source distributed real-time computation system
    • The future of streaming architectures: FAAS. Function as a Service. Extreme microservices.
    • Serverless.com: Build applications comprised of microservices that run in response to events.
  • And much more details into Academy Datastax

That was all for this session.

Many thanks for reading, please leave a comment if you have any quality hint.

Keep on testing, better!

Share:

More posts

  • A woman on the background holding a java logo on her fingers.

    5 Side notes JAX London 2016

    Quick notes from session 5 of JAX London 2016. Java Flight Recorder preseneted by Ola Westin from Oracle.

  • A photo of a soap bubble on a green like forest background.

    Handling error details in Node.js

    This post explores how to manage errors in node js and bubble up the important error detials necessary for higher layers of abstraction.

  • Two persons discussing about some content on a book.

    Software QA Strategy?

    Soon after, when the project is engaged and there is no room for discussions, we realise that what they understood for "strategy" is some kind of Apes plan proper of the mythical film Rise of the Planet of the Apes.