eo-cqrs / ideas Goto Github PK

SQL + eo-event = Event SQL

as SQL we can use jcabi-jdbc, or develop custom eo-postgres/eo-sql on top of that.

plugin for configurations highlighting

@h1alexbel wdyt

component for storing data in cassandra and wrapping around it: CassandraData

Transactional component for distributed transactions and saga

Concept:

Producer<X> producer = new KfProducer<>(new Dataized("json"), "localhost", "...");
    producer.send(new X());
    Consumer<X> consumer =
        new KfConsumer<>("localhost", "...");
    consumer.fetch(15L);
    consumer.fetch();
    Datazied<X> result = consumer.fetch(15L, 3); // wait  and disconnect  // 3 retries
    result.origin(); // returns in json

Job Scheduling in EO way

the component that can do event wrapping around the original object

the logo for the whole eo-cqrs, @h1alexbel what do you think it should look like? can you describe it?

https://www.yegor256.com/2020/05/19/veil-objects.html

component for persisting data in PostgreSQL

Google Cloud Platform Fluent Object-Oriented API

Integration framework for source-target sync up, ETLs, and so on.

public interface Source {

  void stream(Target target, DataStream stream);
}

public interface Target {

  void acquire(Step step);
}

public interface Step<X> {

  final class Simple<X> implements Step<X> {
    private final X data;
  }
}

interface Result<R, F> {

  R outcome(Iterable<F> steps);
 }

xfake - XML In-Memory Storage for your Fake Objects

Simple and elegant Redis external cache API

Kubernetes elegant api