Refactoring Backend: Seperate Producer and Subscription Service - Githubissues

amosproj / amos2023ss01-apache-pulsar-ui

MIT License

5 stars 2 forks source link

Refactoring Backend: Seperate Producer and Subscription Service #206

Open MPSebastian opened 1 year ago

MPSebastian commented 1 year ago

User story

As a developer
I want different service logic to be seperated
So that I can get a better overview of the code base

Acceptance criteria

seperate producer and subscription service

Definition of done (DoD)

Feature is done when the acceptance criteria are fullfiled
Feature is done when there are test where it is necessary and they pass
Feature is done when the linter passes
Feature is done when it is merged onto our main branch (after the code has been reviewed by at least one other person)
Feature is done when the code has been documentend or commented properly

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

nikkite99 commented 1 year ago

Decided not the separate the services. Instead of that i rework some parts of the topicservice to make it more clean.