Forward

Since go-zero integrates web/rpc, some friends in the community will ask me whether go-zero is positioned as a microservice framework. The answer is no. Although go-zero integrates many functions, you can use any one of them independently, or you can develop a single service.

It is not that every service must adopt the design of the microservice architecture.

Create greet service

$ mkdir go-zero-demo

$ cd go-zero-demo

$ go mod init go-zero-demo

$ goctl api new greet

$ go mod tidy

Done.

Take a look at the structure of the greet service

$ cd greet

$ tree

.

├── etc

│   └── greet-api.yaml

├── go.mod

├── greet.api

├── greet.go

└── internal

├── config

│   └── config.go

├── handler

│   ├── greethandler.go

│   └── routes.go

├── logic

│   └── greetlogic.go

├── svc

│   └── servicecontext.go

└── types

└── types.go

It can be observed from the above directory structure that although the greet service is small, it has "all internal organs". Next, we can write business code in greetlogic.go.

Write logic

$ vim greet/internal/logic/greetlogic.go

func (l *GreetLogic) Greet(req types.Request) (*types.Response, error) {

return &types.Response{

Message: "Hello go-zero",

}, nil

}

Start and access the service

• Start service

  $ cd greet

  $ go run greet.go -f etc/greet-api.yaml

  Starting server at 0.0.0.0:8888...

• Access service

  $ curl -i -X GET http://localhost:8888/from/you

  HTTP/1.1 200 OK

  Content-Type: application/json

  Date: Sun, 07 Feb 2021 04:31:25 GMT

  Content-Length: 27

  {"message":"Hello go-zero"}

Source code

greet source code