Setup a simple producer / consumer testing environment in order to proper test all the communications infrastructure#7
Open
feed3r wants to merge 4 commits intoTheG-r-itters:feature/testingfrom
Conversation
Fix the starting script for python kafka consumer and producer. All of them supports the force-rebuild and force-restart option and these are managed accordingly.
The producer should run in a while true, producing messages in an infinite loop
Start script now manages correctly the containers, deleting an already existing container when starting and managing the force-rebuild and force-restart options
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Actually, the purpose of this repository is really basic: just setup a Kafka infrastructure for our project. With this PR, and in this branch, what we want to start is a testing facility that will allow to validate and test all of the core infrastructure.
At the moment (again) it is really simple, and it simply consists of a simple producer and consumer that respectively writes and reads messages on certain topic, actually in one partition.
The idea is to create a testing facility, and infrastructure, using Docker compose and in case testing other technologies (docker swarm? kubernetes in the future?)