<p>Hi, I am working on my first Open Source GO project and am looking for feedback.
Commander is a library that helps you writing applications following the <a href="https://github.com/capitalone/cqrs-manager-for-distributed-reactive-services/blob/master/doc/architecture.png" rel="nofollow">CQRS and Event Sourcing architecture</a>. I am aiming to create a developer friendly library that gets you started quickly. Tests are still a WIP but hope to be finished with them soon. Many thanks!</p>
<p><a href="https://github.com/sysco-middleware/commander" rel="nofollow">https://github.com/sysco-middleware/commander</a></p>
<hr/>**评论:**<br/><br/>aimof: <pre><p>I'm an novice, so I want to know an question for future use.</p>
<p>Why you separate commander and boilerplate as other repositories?</p>
<p>Recently, I often see `repo/cmd/foo` directory strucutre in some projects.</p></pre>Meqube: <pre><p>I wanted to separate them so the boilerplate is not fetched when including the dependency in your project.</p></pre>aimof: <pre><p>Thanks!</p></pre>
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码`
- 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传