You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
To support A/B/n testing, Iter8 provides an SDK. This SDK currently provides 2 APIs:
Lookup() - Identifies a track label that the caller can use to send requests for a given user session. The caller uses the track as an index to route requests.
WriteMetric() - Associates a metric with the version currently associated with the recommended track. Allows caller to ignore the mapping between track and version.
gRPC protocol buffers are language independent. They can be used to generate stubs for many languages. The examples provided took the following approaches:
Node.js - language specific files manually generated and used in example
go - import package from main Iter8 project
Describe the solution you'd like
Developers can manually generate files from the protocol buffer file. However, it would be nice to have libraries/packages for all/any of the supported languages (list from https://grpc.io/docs/languages/):
C/C++
C#
Dart
Go (done)
Java
Kotlin
Node.js
Objective-C
PHP
Python
Ruby
The text was updated successfully, but these errors were encountered:
As an example of the undesirable option: in the Node.js implementation of the sample application, two files were manually generated from a copy of the abn.proto and explicitly included in the main.js.
It would be preferable to refer to an external package that is maintained and updated whenever abn.proto changes.
Is your feature request related to a problem? Please describe.
To support A/B/n testing, Iter8 provides an SDK. This SDK currently provides 2 APIs:
The SDK is implemented using gRPC. Iter8 provides a protocol buffer document and an implementing service. See A/B tutorial for details. Sample code, in Node.js and Go, are provided.
gRPC protocol buffers are language independent. They can be used to generate stubs for many languages. The examples provided took the following approaches:
Describe the solution you'd like
Developers can manually generate files from the protocol buffer file. However, it would be nice to have libraries/packages for all/any of the supported languages (list from https://grpc.io/docs/languages/):
The text was updated successfully, but these errors were encountered: