microservice-bootstrap
microservice-bootstrap copied to clipboard
Separate kinesis from this bootstrap repo
While the capability to consume and produce kinesis streams is a wonderful bootstrap set up, It is a good idea to separate the kinesis consumer itself into a separate NuGet package and consume it from here.
I am referring to the KinesisNet folder in worker service
@jimmyp
Agreed. To be clear, the intention is however to be able to clone and run both the infra and code repos and be consuming events from a stream straight away.
@humblelistener has seperate the Kinesis sample to a seperate project. Next step is to create a nuget package. Possibly in a seperate repo?
thats my idea
On 21 June 2017 at 07:13, JimmyP [email protected] wrote:
@humblelistener https://github.com/humblelistener has seperate the Kinesis sample to a seperate project. Next step is to create a nuget package. Possibly in a seperate repo?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/PageUpPeopleOrg/microservice-bootstrap/issues/29#issuecomment-309893476, or mute the thread https://github.com/notifications/unsubscribe-auth/ACBUOmJPbIvTrjhPrNHhhicmoKGh53Ysks5sGDYBgaJpZM4L-oeV .
-- Technical Adviser PageUp http://www.pageuppeople.com
--
Ideally we could make a PR to https://github.com/sbarski/KinesisNet with our changes that support dot net core and add publishing of a nuget package
Yes
On Fri, 23 Jun 2017 at 7:09 am, JimmyP [email protected] wrote:
Ideally we could make a PR to https://github.com/sbarski/KinesisNet with our changes that support dot net core and add publishing of a nuget package
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/PageUpPeopleOrg/microservice-bootstrap/issues/29#issuecomment-310503463, or mute the thread https://github.com/notifications/unsubscribe-auth/ACBUOmYkgVT0RgCHFb6KRq8sted0aHKDks5sGtgcgaJpZM4L-oeV .
-- Technical Adviser PageUp http://www.pageuppeople.com
--