This is a loosely-coupled mechanism in which services may be added and removed independently of the client. With the broker, the client may never know which servers implement the functionality (and vice versa). Someone else may be monitoring sales of widgets on the site in order to determine whether there's a market for opening a store to sell these widgets etc. Some software robot may subscribe too and contact me offering to transport or insure the things I'm selling. Multiple people may see my ad (subscriber) and offer to buy (method) the items from me. I (client) post a classified ad on some site (broker). Message brokers (e g NATS, Rabbit) provide a higher-level abstraction in which a client sends messages to an intermediate service called a broker (this could be done using gRPC) and the broker may queue messages and either ship them directly to services (push) or wait for a service to check its subscription (pull).Į.g. APIs From RESTful to Event-Driven APIs API Gateway vs. used in machine learning, such as Elasticsearch, MPI, or Kubernetes. GRPC is an alternative to REST, GraphQL, and other mechanisms used to connect clients with servers though some form of API. External interfaces (e.g., REST, gRPC) for the BOSS AI platform to interact with. I (client) call Starbucks (service) and order (method) a coffee. The client is tightly-coupled (often through load-balancers) with servers that implement the methods.Į.g. GRPC is a mechanism by which a client invokes methods on remote (although they needn't be) server. The technologies address different needs. Discuss Vertical Horizontal 40:42 Summary Alex Borysov, Matt McLarty and Michelle Garrett discuss REST, GraphQL, and gRPC, what it takes to get started, and when each is the right/wrong tool.
0 Comments
Leave a Reply. |