konig-kontext
A globally shared, request scoped, context for JVM based gRPC microservices (by konigsoftware)
outbox-inbox-patterns
Repository to support the article "Building a Knowledge Base Service With Neo4j, Kafka, and the Outbox Pattern" (by thegoncalomartins)
konig-kontext | outbox-inbox-patterns | |
---|---|---|
6 | 1 | |
44 | 6 | |
- | - | |
6.9 | 0.0 | |
about 1 month ago | about 2 years ago | |
Kotlin | Kotlin | |
MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
konig-kontext
Posts with mentions or reviews of konig-kontext.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-18.
-
KonigKontext - A globally shared, request scoped, context for JVM based gRPC microservices
It's called KonigKontext, check it out here: https://github.com/konigsoftware/konig-kontext!
-
gRPC request context which caries values across microservice boundaries
Support for multiple keys is in the works! See this issue for updates: https://github.com/konigsoftware/konig-kontext/issues/8
outbox-inbox-patterns
Posts with mentions or reviews of outbox-inbox-patterns.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-22.
-
Building a Knowledge Base Service With Neo4j, Kafka, and the Outbox Pattern
The following diagram describes the final architecture and that’s exactly what I’ve implemented in this small example project to support this article. KrakenD was used as the API Gateway and all the services were written in Kotlin using the Quarkus framework. people-api and movies-api have each a MongoDB database whereas knowledge-base has a Neo4j database.
What are some alternatives?
When comparing konig-kontext and outbox-inbox-patterns you can also consider the following projects:
krotoDC - Protobuf Kotlin Dataclass, Converter & Custom Kotlin Coroutine gRPC Generator
MongoDB - The MongoDB Database
kotlinx.serialization - Kotlin multiplatform / multi-format serialization
kotlin - The Kotlin Programming Language.
kroto-plus - gRPC Kotlin Coroutines, Protobuf DSL, Scripting for Protoc
ApacheKafka - A curated re-sources list for awesome Apache Kafka
grpc-scala-sample - translated from grpc java examples with ScalaPB
spring-cloud-stream-multibinder - 🍀 Spring Cloud Stream Multibinder - Kafka & Kafka Streams
Quarkus - Quarkus: Supersonic Subatomic Java.
Neo4j - Graphs for Everyone
konig-kontext vs krotoDC
outbox-inbox-patterns vs MongoDB
konig-kontext vs kotlinx.serialization
outbox-inbox-patterns vs kotlin
konig-kontext vs kroto-plus
outbox-inbox-patterns vs ApacheKafka
konig-kontext vs grpc-scala-sample
outbox-inbox-patterns vs spring-cloud-stream-multibinder
outbox-inbox-patterns vs Quarkus
outbox-inbox-patterns vs Neo4j