起首咱们用go-micro构建一个效劳。(对于go-micro的应用能够参照民间实例或许文档)
//新建一个微效劳 micro new --type "srv" user-srv
界说咱们的效劳,这里界说两个rpc效劳,Register以及User
// 修正proto syntax = "proto3"; package go.micro.srv.user; service User { rpc Register(RegisterRequest) returns (UserInfo) {} rpc User(UserInfoRequest) returns (UserInfo) {} rpc Stream(StreamingRequest) returns (stream StreamingResponse) {} rpc PingPong(stream Ping) returns (stream Pong) {} } message UserInfoRequest { int64 userId = 1; } message RegisterRequest { string username = 1; string email = 2; string password = 3; } message UserInfo { int64 id = 1; string username = 2; string email = 3; } message StreamingRequest { int64 count = 1; } message StreamingResponse { int64 count = 1; } message Ping { int64 stroke = 1; } message Pong { int64 stroke = 1; }
而后天生执行上面饬令咱们就能够发如今proto文件中多出两个文件。这个proto为咱们天生的,前面会用到。
protoc --proto_path=${GOPATH}/src:. --micro_out=. --go_out=. proto/user/user.proto
写咱们的营业逻辑,修正handle/user.go文件
type User struct{} // Call is a single request handler called via client.Call or the generated client code func (e *User) Register(ctx context.Context, req *user.RegisterRequest, rsp *user.UserInfo) error { log.Log("Received User.Register request") rsp.Id = 1 rsp.Email = req.Email rsp.Username = req.Username return nil } func (e *User) User(ctx context.Context, req *user.UserInfoRequest, rsp *user.UserInfo) error { log.Log("Received User.Register request") rsp.Id = 1 rsp.Email = "741001560@qq.com" rsp.Username = "chensi" return nil } // Stream is a server side stream handler called via client.Stream or the generated client code func (e *User) Stream(ctx context.Context, req *user.StreamingRequest, stream user.User_StreamStream) error { log.Logf("Received User.Stream request with count: %d", req.Count) for i := 0; i < int(req.Count); i++ { log.Logf("Responding: %d", i) if err := stream.Send(&user.StreamingResponse{ Count: int64(i), }); err != nil { return err } } return nil } // PingPong is a bidirectional stream handler called via client.Stream or the generated client code func (e *User) PingPong(ctx context.Context, stream user.User_PingPongStream) error { for { req, err := stream.Recv() if err != nil { return err } log.Logf("Got ping %v", req.Stroke) if err := stream.Send(&user.Pong{Stroke: req.Stroke}); err != nil { return err } } }
最初修正咱们的main.go文件,效劳发现应用时consul。
func main() { //initCfg() // New Service micReg := consul.NewRegistry() service := micro.NewService( micro.Server(s.NewServer()), micro.Name("go.micro.srv.user"), micro.Version("latest"), micro.Registry(micReg), ) // Initialise service service.Init() // Run service if err := service.Run(); err != nil { log.Fatal(err) } }
咱们应用consul做微效劳发现,当然起首你需求装置consul
wget https://releases.hashicorp.com/consul/1.2.0/consul_1.6.1_linux_amd64.zip
unzip consul_1.6.1_linux_amd64.zip
mv consul /usr/local/bin/
启动consul的时分因为正在是内陆虚构机下面,以是咱们能够简略解决
consul agent -dev -client 0.0.0.0 -ui
这时候候能够启动consul的ui了,我内陆vagrant的虚构机192.168.10.100,那末咱们关上的是http://192.168.10.100:8500/ui/dc1/services
启动user-srv的效劳发现consul外面呈现 go.micro.srv.user 的效劳注册信息了
上面来写hyperf的代码了。依照民间文档装置框架,装置的时分rpc需求抉择grpc,需求留意的是你的零碎下面需求装置php7.2以上的版本,swoole版本也需求4.3的版本以上,我用的是最新homestead,以是绝对而言装置这些依赖比拟简略,以是正在此激烈保举。
第一次启动时分民间会要求修正一些php.ini的参数,各人装置要求走就是了。
这局部的流程本人参照民间文档,至于一些扩大的装置能够google或许baidu。
装置好框架之后再根目次上面新建一个grpc以及proto的目次,把go-micro外面user.proto文件复制到hyperf名目的proto的目次之下。而后正在目次下执行饬令
protoc --php_out=plugins=grpc:../grpc user.proto
执行胜利之后会发如今grpc目次下多出两个文件夹。
接上去咱们开端编写client的代码,正在hyperf名目的app目次下新建一个Grpc的目次而且新建一个UserClient.php的文件
namespace App\Grpc; use Go\Micro\Srv\User\RegisterRequest; use Go\Micro\Srv\User\UserInfo; use Hyperf\GrpcClient\BaseClient; class UserClient extends BaseClient { public function Register(RegisterRequest $argument) { return $this->simpleRequest( '/user.User/Register', $argument, [UserInfo::class, 'decode'] ); }
对于这一块的代码,其实民间文档写患上特地具体,详细能够参照民间文档。
新建一个路由
Router::addRoute(['GET', 'POST', 'HEAD'], '/grpc', 'App\Controller\IndexController@grpc');
编写管制器
public function grpc () { $client = new \App\Grpc\UserClient('127.0.0.1:9527', [ 'credentials' => null, ]); $request = new RegisterRequest(); $request->setEmail("741001560@qq.com"); $request->setUsername("chensi"); $request->setPassword("123456"); /** * @var \Grpc\HiReply $reply */ list($reply, $status) = $client->Register($request); $message = $reply->getId(); return [ 'id' => $message ]; }
这时候候还需求吧根目次下的grpc目次加载出去。修正composer.json文件
``` // psr-4 上面新增两个行 "autoload": { "psr-4": { "App\\": "app/", "GPBMetadata\\": "grpc/GPBMetadata", "Go\\": "grpc/Go" }, "files": [] }
而后执行composer dump-autoload饬令。而后启动hyperf名目,关上阅读器输出http://192.168.10.100:9501/grpc回车,这时候候咱们就能看到后果了。
这时候候咱们会发现一个成绩,那就是consul正在client端压根没用到,正在代码中咱们仍是需求指明咱们的端标语。而后再看看民间文档实际上是支持consul的,那末将代码革新下。
正在app下新建一个Register的目次创立一个文件ConsulServices.php,而后开端编写效劳发现的代码,装置consul包当前,因为民间提供的consul包不文档以是需求本人去看源代码。民间正在consul提供的api下面做了简略的封装,如KV、Health等,正在实例化话的时分需求穿一个客户端过来。上面提供一个简略的实例。
<?php declare(strict_types=1); namespace App\Register; use Hyperf\Consul\Health; use Psr\Container\ContainerInterface; use Hyperf\Guzzle\ClientFactory; class ConsulServices { public $servers; private $container; public function __construct(ContainerInterface $container) { $this->container = $container; } public function getServers() { $health = new Health(function () { return $this->container->get(ClientFactory::class)->create([ 'base_uri' => 'http://127.0.0.1:8500', ]); }); $resp = $health->service("go.micro.srv.user"); $servers = $resp->json(); if (empty($servers)){ $this->servers = []; } foreach ($servers as $server) { $this->servers[] = sprintf("%s:%d",$server['Service']['Address'],$server['Service']['Port']); } } }
这时候候发现一个成绩假如每一次申请过去都去申请一次必定给consul造成很年夜的负荷。既然用到了swoole框架能够正在每一次swoole启动的时分去申请一次,而后把效劳发现的信息存起来。修正设置装备摆设文件server。
'callbacks' => [ // SwooleEvent::ON_BEFORE_START => [Hyperf\Framework\Bootstrap\ServerStartCallback::class, 'beforeStart'], SwooleEvent::ON_BEFORE_START => [\App\Bootstrap\ServerStartCallback::class, 'beforeStart'], SwooleEvent::ON_WORKER_START => [Hyperf\Framework\Bootstrap\WorkerStartCallback::class, 'onWorkerStart'], SwooleEvent::ON_PIPE_MESSAGE => [Hyperf\Framework\Bootstrap\PipeMessageCallback::class, 'onPipeMessage'], ], 能够正在ServerStartCallback类外面申请consul进行效劳发现 前面拿到参数就行了。 namespace App\Bootstrap; use App\Register\ConsulServices; class ServerStartCallback { public function beforeStart() { $container = \Hyperf\Utils\ApplicationContext::getContainer(); $container->get(ConsulServices::class)->getServers(); } }
革新一下原来的管制器
public function grpc () { $container = \Hyperf\Utils\ApplicationContext::getContainer(); $servers = $container->get(ConsulServices::class)->servers; if (empty($servers)) { return [ 'errCode' => 1000, 'msg' => '效劳没有存正在', ]; } $key = array_rand($servers,1); // 哈哈哈一个简略的负载平衡 $hostname = $servers[$key]; $client = new \App\Grpc\UserClient($hostname, [ 'credentials' => null, ]); $request = new RegisterRequest(); $request->setEmail("741001560@qq.com"); $request->setUsername("chensi"); $request->setPassword("123456"); /** * @var \Grpc\HiReply $reply */ list($reply, $status) = $client->Register($request); $message = $reply->getId(); return [ 'id' => $message ]; }
重启效劳,这时候候而后刷新阅读器尝尝。这时候候一个简略基于go rpc server以及php client的微效劳就搭建实现了。当然了这时候候尚未心跳机制,hyperf官网提供了一个按时器的性能,咱们按时去刷效劳发现就行了。
以上就是go-micro+php+consul完成简略的微效劳的具体内容,更多请存眷资源魔其它相干文章!
标签: php php开发教程 php开发资料 php开发自学 consul go-micro
抱歉,评论功能暂时关闭!