finished unit 1 and 2#86
Open
aylonsk wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Unit 1:
Producer side: Implemented the mqProducerInterface and tested using publish.py script through docker
Consumer side: Implemented mqConsumerInterface, declared queue + exchange, tested using consume.py script and
Testing: tested both using publish.py and consume.py scripts respectively, and confirming results through RabbitMQ page.
Unit 2:
Producer side: Switched the producer to a topic exchange (Tech Lab Topic Exchange), implemented routing keys as stock.., and wired publish.py to read --ticker, --price, and --sector from the command line and publish UTF-8 messages.
Consumer side: Implemented the topic consumer interface: declare the topic exchange, create a named queue, bind with a wildcard binding key stock.*., then consume and ack/print messages. Wired consume.py to read --sector and --queue from the command line so each consumer can use a distinct queue name.
Testing: Started two consumers (e.g. tech and healthcare sectors with different queue names), ran publish.py three times with tech, healthcare, and a third sector, with the first two messages only reaching the matching consumer and the third not matching either queue. Verified routing in the RabbitMQ management UI if needed.