[Meeting Minutes] Discussion about Go Directory Structure for Manager API

[JunXu Chen <ch...@apache.org>]

In the last night,
we discussed about Go Directory Structure for Manager API, recorded the
following conclusions:

- Standardization of the project structure: It has been evolving according
to https://github.com/golang-standards/project-layout, and the conf and log
directories need to be included in internal at present

- The current hierarchical structure of the API layer is too single and
does not expand the business logic space for users: the manager-api will
have more business logic injections, and the meeting can be held separately
to discuss the evolution strategy and direction of the architecture, while
meeting business needs Also consider giving users room to expand logic.
Also improve development documentation

- Framework standardization: The current application layer framework
(droplet) will be improved in the later stage, and more access layer
frameworks will be covered at the same time (there are currently gin,
go-restful, and fasthttp. grpc. gnet planned).

- After verification, authorization, etc., a separate meeting will be
discussed. The design can refer to https://github.com/ory/hydra to decouple
the user verification process and allow users to connect to their own user
system.

- Guildes or similar HowTo guides are needed in the document. Both users
and us can add scenarios for APISIX (such as how to do service discovery,
how to customize development, etc.) to facilitate later readers to read.


Participants:

YuanSheng Wang
Vinci
Wei Jin
Hang Li
Junxu Chen