platform-docs/catalog/component/default/petclinic

title, generated_by, generated_at, human_edited, source_entity, source_repo

title	generated_by	generated_at	human_edited	source_entity	source_repo
Petclinic	documentor-agent	2026-05-05T10:50:01+00:00	false	Component/default/petclinic	https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2

Petclinic

A Spring Boot–based application for managing veterinary clinics, including appointments, customers, and pets.

Overview

The Petclinic service is a Java-based application built using Spring Boot. It provides functionality for managing veterinary clinic operations, including customer records, pet details, and appointment scheduling. The application is designed to be lightweight and modular, making it suitable for deployment in various environments.

Originally sourced from the Spring Petclinic project, this service has been scaffolded and enhanced using the Backstage Application Migration Factory template. It includes OpenTelemetry instrumentation for observability and integrates with ArgoCD for continuous deployment. The service is deployed in the demo-apps namespace and is part of the broader petclinic-demo-jonathan-scaf-2 system.

Repository

Field	Value
Source Repo	https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2
Branch	main
ArgoCD App	petclinic-demo-jonathan-scaf-2
Namespace	demo-apps

Architecture

• The service is based on the Spring Boot framework, leveraging its modularity and ease of integration.
• OpenTelemetry auto-instrumentation is applied via a Kustomize overlay, enabling detailed observability for traces, metrics, and logs.
• Continuous deployment is managed by ArgoCD, which syncs changes from the main branch to the demo-apps namespace.
• The application supports multiple database configurations, including H2 (default), MySQL, and PostgreSQL, with profiles for each.

Configuration

Configuration	Description
spring.profiles.active	Specifies the active Spring profile (mysql, postgres, or default h2).
Database URLs	H2: jdbc:h2:mem:<uuid> (default), MySQL: docker-compose up mysql, PostgreSQL: docker-compose up postgres.
OpenTelemetry Endpoint	http://otel-collector.monitoring.svc.cluster.local:4318.

Operations

Local Development

1. Clone the repository:

   git clone https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2.git
   cd petclinic-demo-jonathan-scaf-2
   

2. Run the application:
   • Maven: ./mvnw spring-boot:run
   • Gradle: ./gradlew bootRun
3. Access the application at http://localhost:8080.

Deployment

Changes pushed to the main branch are automatically synced by ArgoCD to the demo-apps namespace. To roll back, use the ArgoCD UI or revert the Git commit.

Database Setup

• Default: In-memory H2 database.
• Persistent options: MySQL or PostgreSQL, configured via Spring profiles.

Rollback

1. Open the ArgoCD UI.
2. Select History and Rollback.
3. Choose the desired revision and click Rollback.

Observability

• Grafana Dashboard: OpenTelemetry Application Observability.
• Alerts: Configured via Grafana, filtered by app=petclinic.

Not configured — see platform observability docs for additional details.

Dependencies

• component:default/argocd-service
• resource:default/k6-operator
• resource:default/otel-collector
• resource:default/veterinary-platform