#
eventually-consistent
Here are 24 public repositories matching this topic...
A tool for building distributed applications.
-
Updated
Mar 27, 2020 - Go
Microservices Event Sourcing 是一个微服务架构的在线购物网站，使用Spring Boot、Spring Cloud、Spring Reactor、OAuth2、CQRS 构建，实现了基于Event Sourcing的最终一致性，提供了构建端到端微服务的最佳实践
angularjs
ecommerce
oauth2
spring-boot
mongodb
microservice
neo4j
event-sourcing
event-driven
springcloud
eventually-consistent
-
Updated
May 19, 2017 - Java
A high-performance framework for eventually consistent distributed event traceability based on the Virtual Actor model.
-
Updated
Sep 14, 2020 - C#
CRDT Tutorial for Beginners (a digestible explanation with less math!)
-
Updated
Jun 29, 2020
Delta State-based CRDTs in Javascript
-
Updated
Nov 26, 2019 - JavaScript
The .NET omega agent for Apache incubator-servicecomb-saga https://github.com/apache/servicecomb-pack
-
Updated
Jan 7, 2019 - C#
Eventually consistent distributed in-memory cache Go library
-
Updated
May 1, 2019 - Go
An eventual consistency framework based on Event Sourcing and CQRS on top of light-4j and Kafka
kafka
cqrs
ddd
event
event-sourcing
entity
aggregate
event-driven-microservices
event-driven
saga
eventually-consistent
eventuate-framework
-
Updated
Feb 29, 2020 - Java
Distributed KV database with causality tracking
-
Updated
Oct 21, 2018 - Rust
jlowellwofford
commented
Nov 26, 2019
Currently, buildlayer0.sh does not pass shellchecker. It should. It probably needs to be generally cleaned up a bit.
An Eventual Leader Election Library for Erlang
-
Updated
Sep 24, 2020 - Erlang
Eventually consistent lock-free (when reading) synchronization primitive
-
Updated
Jun 12, 2019 - Rust
A delta-state block-wise sequence CRDT
-
Updated
Sep 26, 2020 - TypeScript
A threadsafe way to publish data, just stick it on the pinboard
-
Updated
Nov 7, 2019 - Rust
Reliable eventual consistency for Microservices
microservices
microservices-architecture
transaction-manager
eventually-consistent
eventual-consistency
-
Updated
Oct 10, 2020 - Java
An Eventually consistent key-Value store that borrows designs from Dynamo and Cassandra.
-
Updated
Jul 25, 2018 - Java
Eventually Consistent Event Sourced With CQRS E-Commerce Application In MicroService Architecture And DDD
microservices
cqrs
ddd
event-sourcing
microservices-architecture
eventually-consistent
cqrs-ecommerce-application
-
Updated
Oct 19, 2017
Distributed Key-Value store that borrows the designs from DynamoDB and implements eventual consistency for High availability
java
distributed-systems
key-value
dynamodb
distributed-computing
cassandra-database
eventually-consistent
-
Updated
Jan 26, 2018 - Java
lightweight PersistentView implementation with PersistenceQuery
-
Updated
Sep 5, 2017 - Scala
A partner and I created a Fault Tolerant and Scalable Key-Value Store using python and flask. It is fault tolerant using multiple back ups to protect data from loss, comes to eventual consistency within 5 seconds, and can automatically update key/values on revived nodes.
-
Updated
Mar 18, 2018 - Python
A project demonstrating eventually consistence via rocketmq
-
Updated
Jul 1, 2018 - Java
Simple and embeded membership framework for service discovery and cluster management
-
Updated
Oct 8, 2020 - Go
Example of an eventually consistent application
-
Updated
Oct 22, 2019 - Java
Improve this page
Add a description, image, and links to the eventually-consistent topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the eventually-consistent topic, visit your repo's landing page and select "manage topics."
Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.
This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients