Rationale:

cosmic-river aims distributed Event-Driven workflows as generic, composable tool

motivation

I want to gain more pragmatic knowledge on following for me unfamiliar concepts:

  • Message Brokers: https://en.wikipedia.org/wiki/Message_broker

  • I will build the project with Clojure, a Lisp dialect with code-as-data philosophy. (https://clojure.org/)

The project itself has already a design and a scope but I will update it step by step for allowing freedom to experiment.

https://en.wikipedia.org/wiki/Cosmic_ocean

Looking for mad skills in:

clojure jvm functionalprogramming lisp distributedsystems distribution clojurescript

This project is part of:

Hack Week 18

Activity

  • 3 months ago: dmaiocchi liked cosmic-river
  • 3 months ago: dmaiocchi added keyword "clojurescript" to cosmic-river
  • 3 months ago: dmaiocchi added keyword "distribution" to cosmic-river
  • 3 months ago: dmaiocchi added keyword "distributedsystems" to cosmic-river
  • 3 months ago: dmaiocchi added keyword "lisp" to cosmic-river
  • Show History

    Comments

    • dmaiocchi
      3 months ago by dmaiocchi | Reply

      day 01:

      During the 1st day of my hackweek I achieved the core design and schema of cosmic-river. I have draw the most components and their responsibilities, in a lightweight way.

      It has already some functionality which however cannot be used already.

      In the next days I plan to spend time on the message-brokers parts and this is the unfamiliar part of my hackweek, so it can take some times but still an exciting part ;)

      Thanks to interactive programming I was able to debug, code in a revolutionary workflow. I was using emacs + CIDER.

      https://docs.cider.mx/cider/usage/interactive_programming.html

    • dmaiocchi
      3 months ago by dmaiocchi | Reply

      day 2

      During second day I have learned concept with rabbitmq and message broker. ( I had already some theory background).

      I will focus with rabbitmq but I choosed to make cosmic-river composable, so an user could choose Kafka instead of rabbitmq.

      I have also designed the first skeleton with rabbitmq and continue on this model producer/consumer (server/client).

      In the project itself I needed to refactor things and create two different applicaitication. THe scaffold is ready and i plan to continue to work with.

    • dmaiocchi
      3 months ago by dmaiocchi | Reply

      day 3

      All client/server rabbitmq part was improved.

    • dmaiocchi
      3 months ago by dmaiocchi | Reply

      day4:

      Today I will work on serialization part and implement filters

    • dmaiocchi
      3 months ago by dmaiocchi | Reply

      day 4:

      • Improved documentation and presentation ( allthough I need to document the specification to configuration).
      • Data serialization over network done
      • Refactoring of the various namespaces.

      • Continuing working on the filter for events to be generic and parameterizable

    Similar Projects

    help clojure upstream with clj-common with some PR and contributions by dmaiocchi

    Rationale:

    There is around in the cloju...


    Uyuni (property based testing (with (lisp) )) by dmaiocchi

    I will not have the time for bootstrapping this...


    Uyuni (property based testing (with (lisp) )) by dmaiocchi

    I will not have the time for bootstrapping this...


    help clojure upstream with clj-common with some PR and contributions by dmaiocchi

    Rationale:

    There is around in the cloju...


    MicroOS Desktop by RBrownSUSE

    [Video Recording of openSUSE Conference sessio...