From PHP and REST to gRPC and Go

Transcript

1. From PHP and REST To gRPC and Go Winnipeg, December 4 2019 Yuriy Tuz Bold Commerce @yuriytuz
2. #GoTurns10
3. whoami
4. Objectives • Personal experience • Why gRPC • gRPC in GO ◦ Simple implementation
5. In the beginning • Laravel 4.x / 5.x • PHP 7.x ◦ Introduced types
6. Back in the day
7. REST (HTTP + JSON) • Not a bad solution • Service to service communications • JSON is not type safe in PHP • (De)Serialization performance • Text protocol
8. Thank you Questions?
9. REST in Laravel • api.php • Magic • response()->json([???]) • Docs accuracy
10. Problem • Technology is driving demand • Languages and platforms ◦ Different dev experience • Software architecture is evolving ◦ Microservices and containers ◦ CI/CD
11. An Idea
12. An Idea • Bloated service ◦ 1000+ lines • Hack Day • How?
13. No Idea
14. How/why? • Why split? • Why Go? • Why not REST (HTTP+JSON)? ◦ No formal contract ◦ Hard to implement correctly
15. Possible Solution
16. What do we need? • PHP RPC client • RPC server
17. Implementation/Findings • PHP client not fun ◦ Working POC • First experience with Go • Refactoring • Benchmarks ◦ ~100x faster
18. time.Now()
19. Stack • Protocol buffers + gRPC • Thanks Google
20. Protocol buffers are a language-neutral, platform-neutral extensible mechanism for serializing structured data. Protocol Buffers
21. What does this mean? • Serialization mechanism • Interface description language
22. Serialization Mechanism • 0a 05 68 65 6c 6c 6f • 68 65 6c 6c 6f -> hello • 05 -> length of “hello” • 0a is “0000 1010”, so • field_number = 1 • wire_type = 2 (length delimited)
23. Interface Definition Language message Person { string name = 1; } Interface for your API
24. gRPC • Open source messaging system by Google that can run anywhere • Low latency • Highly scalable • Great for distributed systems • Accurate, efficient, language independent
25. Adopted by many (and more)
26. Let’s do it
27. echo.proto
28. Let’s generate • protoc --go_out=:. ./echo.proto ◦ Default protobuf generation • protoc --go_out=plugins=grpc:. ./echo.proto ◦ Client and Server interface ◦ gRPC
29. Success!
30. Server
31. Generated Interface
32. Server implementation
33. Server Spin up server
34. Client
35. Client interface
36. Client
37. So far • Server • Client
38. New Requirement Logging
39. gRPC middleware • Server or Client • Few exist in gRPC ecosystem ◦ Prometheus ◦ Open tracing • https://github.com/grpc-ecosystem/go-grpc-middleware
40. How?
41. gRPC middleware
42. >1 interceptor?
43. Directory structure • Client & server implementation • echo.pb.go ◦ gRPC generated • echo.proto ◦ API definition
44. Helpful tools
45. grpcurl • “curl” for gRPC • Requires server reflection
47. Examples
48. grpcui • Postman for RPC • Also requires reflection
51. Final thoughts The good • Code generation ◦ Less error prone • API spec • gRPC ◦ HTTP2 + language support • Type safety • Plugins • Dev ramp up speed The bad • Code generation • Model conversions ◦ Nested messages • Hard/scary to get started ◦ Documentation • API versioning
52. TL;DR • Use gRPC + Go • Generate code • Implement stubs • Profit
53. Credits/Useful links • Gopher art by Ashley McNamara ◦ https://github.com/ashleymcnamara/gophers • gRPC ◦ https://grpc.io/ • Google API Design Guide ◦ https://cloud.google.com/apis/design/ • Protobuf Style Guide ◦ https://developers.google.com/protocol-buffers/docs/style • rpcurl and grpcui ◦ https://github.com/fullstorydev
54. Questions? @yuriytuz