Where would validation and authorization (permissions) fit in Standard Package Layout?

polaris · 2017-01-05 19:00:10 · 992 次点击    
这是一个分享于 2017-01-05 19:00:10 的资源,其中的信息可能已经有所发展或是发生改变。

The post Standard package Layout discusses how to layer different functionalities by wrapping the same interface.

For instance, myapp.UserCache wraps postgres.UserService, where both satisfy myapp.UserService` interface.

What would be a good approach to add validation and authorization (who has permission which endpoint, not to be mistaken with authentication)?

Would it be a good idea to have validation and authorization also as structures which satisfy myapp.UserService? So it would like:

Authorization wraps validation wraps caching wraps datastore

At this point, the service interface feels like what middleware do.

One advantage of authorization satisfying myapp.UserService is that, if it does not, then you can find out which service endpoints are not covered at compile time.

Maybe /u/benbjohnson could join this discussion too!


入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889

992 次点击  
加入收藏 微博
0 回复
暂无回复
添加一条新回复 (您需要 登录 后才能回复 没有账号 ?)
  • 请尽量让自己的回复能够对别人有帮助
  • 支持 Markdown 格式, **粗体**、~~删除线~~、`单行代码`
  • 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
  • 图片支持拖拽、截图粘贴等方式上传