@iluwatar what feature you wanted to add i can do

Hey @iluwatar, I can pick this task up.

This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.

still working on it, albeit a bit slow :)
The stale label can be removed

This issue is stale because it has been open 60 days with no activity.

@CoderSleek , are you working on this..?

@quantdevv hey, i was working on this yes but not anymore due to my work. it's available to take up i believe.

Thanks @iluwatar @CoderSleek , i'll have a look on this.

Hey @iluwatar , i want to discuss something on this... is there any dedicated server to discuss any kind issue..?

Hey @iluwatar , i want to discuss something on this... is there any dedicated server to discuss any kind issue..?

Try Gitter channel here: https://app.gitter.im/#/room/#iluwatar_java-design-patterns:gitter.im

Hi @iluwatar , here i'm planning to implement this micro-service pattern in below architecture .. would you like to review it once..?

Here will create two services polling-service & subscriber-service. as i made two to keep it true microservice architecture.

1. polling-service -> which will handles the periodically check for update or change in datasource & schedule , polling controller alongwith rest-controller so can be tested manually... or can be used either way.

2. subscriber service -> this contains the kafka MQ , which consume the published message by polling controller & schedular ...

the dummy structure will be like this..

Data-source ------> polling service (polling schedular, controller (publish)) ----> MQ (Kafka) -----> notification

let me know if you have any suggestion on this.. or else i'll proceed with it.

Yes, sounds good @quantdevv 👍