RRepoGEO

REPOGEO REPORT · LITE

spring-petclinic/spring-petclinic-microservices

Default branch main · commit 305a1f13 · scanned 6/30/2026, 10:52:02 AM

GitHub: 2,150 stars · 2,777 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface spring-petclinic/spring-petclinic-microservices, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition README opening to emphasize reference architecture and learning value

    Why:

    CURRENT
    This microservices branch was initially derived from AngularJS version to demonstrate how to split sample Spring application into microservices. To achieve that goal, we use Spring Cloud Gateway, Spring Cloud Circuit Breaker, Spring Cloud Config, Micrometer Tracing, Resilience4j, Open Telemetry and the Eureka Service Discovery from the Spring Cloud Netflix technology stack.
    COPY-PASTE FIX
    This repository provides a comprehensive **reference architecture and learning resource** for building distributed, resilient microservices with Spring Cloud. It evolves the classic Spring PetClinic application into a microservices landscape, demonstrating best practices for service discovery (Eureka), circuit breakers (Resilience4j), distributed tracing (OpenTelemetry, Micrometer Tracing), monitoring (Prometheus, Grafana), and configuration management (Spring Cloud Config).
  • mediumhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://spring.io/projects/spring-petclinic
  • lowreadme#3
    Add a 'How to use this project' section to the README

    Why:

    COPY-PASTE FIX
    ## How to use this reference architecture
This project is ideal for developers and architects looking to:
*   Learn how to decompose a monolithic Spring application into microservices.
*   Understand practical implementations of Spring Cloud components like Eureka, Resilience4j, and Spring Cloud Config.
*   Explore patterns for distributed tracing, monitoring, and resilience in a microservices environment.
*   Use a working example as a starting point for their own Spring Cloud microservices projects.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface spring-petclinic/spring-petclinic-microservices
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Eureka
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Eureka · recommended 2×
  2. Resilience4j · recommended 2×
  3. Hystrix · recommended 2×
  4. Spring Boot · recommended 1×
  5. Spring Cloud · recommended 1×
  • CATEGORY QUERY
    How to build resilient Java microservices with distributed tracing and monitoring?
    you: not recommended
    AI recommended (in order):
    1. Spring Boot
    2. Spring Cloud
    3. Spring Cloud Sleuth
    4. Prometheus
    5. Grafana
    6. Eureka
    7. Consul
    8. Resilience4j
    9. Spring Cloud CircuitBreaker
    10. Spring Cloud Gateway
    11. Micronaut
    12. Micronaut Tracing
    13. Micrometer
    14. OpenTelemetry
    15. Zipkin
    16. Micronaut Resilience
    17. Quarkus
    18. SmallRye Fault Tolerance
    19. Dropwizard
    20. Jetty
    21. Jersey
    22. Jackson
    23. Dropwizard Metrics
    24. Brave
    25. Hystrix
    26. Vert.x
    27. Circuit Breaker (Vert.x)
    28. Jaeger
    29. Grafana Tempo
    30. Alertmanager
    31. ELK Stack
    32. Elasticsearch
    33. Logstash
    34. Kibana
    35. Loki

    AI recommended 35 alternatives but never named spring-petclinic/spring-petclinic-microservices. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Recommendations for a framework to implement service discovery, circuit breakers, and configuration management?
    you: not recommended
    AI recommended (in order):
    1. Spring Cloud Netflix
    2. Spring Cloud Config
    3. Eureka
    4. Hystrix
    5. Resilience4j
    6. HashiCorp Consul
    7. Istio
    8. Linkerd
    9. Kubernetes ConfigMaps
    10. Kubernetes Secrets
    11. External Secrets Operator
    12. Alibaba Nacos
    13. Sentinel
    14. etcd
    15. Polly

    AI recommended 15 alternatives but never named spring-petclinic/spring-petclinic-microservices. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of spring-petclinic/spring-petclinic-microservices?
    pass
    AI named spring-petclinic/spring-petclinic-microservices explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts spring-petclinic/spring-petclinic-microservices in production, what risks or prerequisites should they evaluate first?
    pass
    AI named spring-petclinic/spring-petclinic-microservices explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo spring-petclinic/spring-petclinic-microservices solve, and who is the primary audience?
    pass
    AI named spring-petclinic/spring-petclinic-microservices explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of spring-petclinic/spring-petclinic-microservices. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/spring-petclinic/spring-petclinic-microservices.svg)](https://repogeo.com/en/r/spring-petclinic/spring-petclinic-microservices)
HTML
<a href="https://repogeo.com/en/r/spring-petclinic/spring-petclinic-microservices"><img src="https://repogeo.com/badge/spring-petclinic/spring-petclinic-microservices.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

spring-petclinic/spring-petclinic-microservices — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite