zeromicro / zeromicro/zero-doc
proto接口文件的隔离
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 600
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
我是第一次使用zero框架，有几个问题交流一下：
- 关于proto接口文件的隔离
建议参考一下micro的设计，
proto 接口文件应该抽象出来，
这样proto接口文件的修改和业务模块都是独立
2.rpc业务模块直接的调用不应该直接引用，应该是和proto一样抽象至独立的package中
谢谢，这是我在使用中的一点建议。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the current zero framework package structure and comparing it with micro's design, then determine how proto interfaces and RPC business modules should be isolated. Done requires an agreed architectural scope and implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100