Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop "service" suffix, and standardize names #1788

Open
puckpuck opened this issue Nov 21, 2024 · 1 comment
Open

Drop "service" suffix, and standardize names #1788

puckpuck opened this issue Nov 21, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@puckpuck
Copy link
Contributor

When running the demo, it is composed of 25+ individual containers/components/microservices. The names of these components are carried over from the demo's original roots, and several additional services and external components were added to support the demo's goal of showcasing OpenTelemetry across various languages and frameworks.

Currently, most services in the demo have a service suffix as part of their image and OpenTelemetry service name. Containers will have a -service suffix. Some services, such as the product catalog service, have a space in their name. The container name will be hyphenated, but the service/pod and OpenTelemetry definitions will have this as a single word.

A well-understood, concise, and consistent naming for all services would significantly improve the usability of the demo for users in observability tooling as well as contributors that support this effort. I propose dropping the service suffix from all services and using a hyphen (-) for spaces in names. The names should be consistent across the docker compose service, container name, OpenTelemetry service name, and Kubernetes deployment name.

The following table describes the current and suggested name for each Demo component:

Current Name Suggested Name
accountingservice accounting
adservice ad
cartservice cart
checkoutservice checkout
currencyservice currency
emailservice email
flagd flagd
flagd-ui flagd-ui
frauddetectionservice fraud-detection
frontend frontend
frontendproxy frontend-proxy
frontend-web frontend-web
grafana grafana
imageprovider image-provider
jaeger jaeger
kafka kafka
loadgenerator load-generator
opensearch opensearch
otelcollector otel-collector
paymentservice payment
productcatalogservice product-catalog
prometheus prometheus
quotesservice quote
recommendationsservice recommendation
shippingservice shipping
valkey-cart valkey

I welcome feedback and suggestions on this proposal. This is something we can also discuss during the next SIG meeting.

@puckpuck puckpuck added the enhancement New feature or request label Nov 21, 2024
@julianocosta89
Copy link
Member

Great suggestion!
+1 to that.

I'd just keep the valkey-cart. But fine in going to only valley as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants