{"id":20791920,"url":"https://github.com/spring-petclinic/spring-petclinic-cloud","last_synced_at":"2025-04-04T23:09:53.797Z","repository":{"id":43218709,"uuid":"213207127","full_name":"spring-petclinic/spring-petclinic-cloud","owner":"spring-petclinic","description":"Fork of the Spring Cloud Microservices project packaged to be deployed on several Cloud platforms: Kubernetes and Cloud Foundry","archived":false,"fork":false,"pushed_at":"2024-08-01T21:32:43.000Z","size":6417,"stargazers_count":144,"open_issues_count":8,"forks_count":255,"subscribers_count":4,"default_branch":"master","last_synced_at":"2025-03-28T22:14:41.336Z","etag":null,"topics":["cloud-foundry","docker","kubernetes","spring-cloud","tanzu","wavefront"],"latest_commit_sha":null,"homepage":"","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/spring-petclinic.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-10-06T16:53:40.000Z","updated_at":"2025-03-25T18:07:35.000Z","dependencies_parsed_at":"2024-11-24T16:01:48.436Z","dependency_job_id":null,"html_url":"https://github.com/spring-petclinic/spring-petclinic-cloud","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-petclinic%2Fspring-petclinic-cloud","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-petclinic%2Fspring-petclinic-cloud/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-petclinic%2Fspring-petclinic-cloud/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/spring-petclinic%2Fspring-petclinic-cloud/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/spring-petclinic","download_url":"https://codeload.github.com/spring-petclinic/spring-petclinic-cloud/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247261612,"owners_count":20910108,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cloud-foundry","docker","kubernetes","spring-cloud","tanzu","wavefront"],"created_at":"2024-11-17T15:47:47.109Z","updated_at":"2025-04-04T23:09:53.778Z","avatar_url":"https://github.com/spring-petclinic.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Distributed version of the Spring PetClinic - adapted for Cloud Foundry and Kubernetes \n\n[![Build Status](https://travis-ci.org/spring-petclinic/spring-petclinic-cloud.svg?branch=master)](https://travis-ci.org/spring-petclinic/spring-petclinic-cloud/) [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)\n\nThis microservices branch was initially derived from the [microservices version](https://github.com/spring-petclinic/spring-petclinic-microservices) to demonstrate how to split sample Spring application into [microservices](http://www.martinfowler.com/articles/microservices.html).\nTo achieve that goal we use Spring Cloud Gateway, Spring Cloud Circuit Breaker, Spring Cloud Config, Spring Cloud Sleuth, Resilience4j, Micrometer and the Eureka Service Discovery from the [Spring Cloud Netflix](https://github.com/spring-cloud/spring-cloud-netflix) technology stack. While running on Kubernetes, some components (such as Spring Cloud Config and Eureka Service Discovery) are replaced with Kubernetes-native features such as config maps and Kubernetes DNS resolution.\n\nThis fork also demostrates the use of free distributed tracing with Tanzu Observability by Wavefront, which provides cloud-based monitoring of  Spring Boot applications with 5 days of history.\n\n\n  * [Understanding the Spring Petclinic application](#understanding-the-spring-petclinic-application)\n  * [Compiling and pushing to Cloud Foundry:](#compiling-and-pushing-to-cloud-foundry)\n  * [Compiling and pushing to Kubernetes](#compiling-and-pushing-to-kubernetes)\n    + [Choose your Docker registry](#choose-your-docker-registry)\n    + [Setting things up in Kubernetes](#setting-things-up-in-kubernetes)\n    + [Settings up databases with helm](#settings-up-databases-with-helm)\n    + [Deploying the application](#deploying-the-application)\n  * [Starting services locally without Docker](#starting-services-locally-without-docker)\n  * [Starting services locally with docker-compose](#starting-services-locally-with-docker-compose)\n  * [In case you find a bug/suggested improvement for Spring Petclinic Microservices](#in-case-you-find-a-bug-suggested-improvement-for-spring-petclinic-microservices)\n  * [Database configuration](#database-configuration)\n    + [Start a MySql database](#start-a-mysql-database)\n    + [Use the Spring 'mysql' profile](#use-the-spring--mysql--profile)\n  * [Custom metrics monitoring](#custom-metrics-monitoring)\n    + [Using Prometheus](#using-prometheus)\n    + [Using Grafana with Prometheus](#using-grafana-with-prometheus)\n    + [Custom metrics](#custom-metrics)\n  * [Looking for something in particular?](#looking-for-something-in-particular-)\n  * [Interesting Spring Petclinic forks](#interesting-spring-petclinic-forks)\n- [Contributing](#contributing)\n\n\n## Understanding the Spring Petclinic application\n\n[See the presentation of the Spring Petclinic Framework version](http://fr.slideshare.net/AntoineRey/spring-framework-petclinic-sample-application)\n\n[A blog bost introducing the Spring Petclinic Microsevices](http://javaetmoi.com/2018/10/architecture-microservices-avec-spring-cloud/) (french language)\n\nYou can then access petclinic here: http://localhost:8080/\n\n![Spring Petclinic Microservices screenshot](./docs/application-screenshot.png?lastModify=1596391473)\n\n\n\n\n## Compiling and pushing to Cloud Foundry:\n\nThe samples below are using Tanzu Application Service (previously Pivotal Cloud Foundry) as the target Cloud Foundry deployment, some adjustments may be needed for other Cloud Foundry distributions.\n\nPlease make sure you have the latest `cf` cli installed: https://docs.cloudfoundry.org/cf-cli/install-go-cli.html  \nFor more information on Tanzu Application Service, see: https://docs.pivotal.io/application-service/2-10/overview/dev.html  \nFor a list of available Cloud Foundry distributions, see: https://www.cloudfoundry.org/certified-platforms/  \nFor local testing and development, you can use PCF Dev: https://docs.pivotal.io/pcf-dev/  \n\nThis application uses Wavefront as a SaaS that can provide free Spring Boot monitoring and Open Tracing for your application. If you'd like to remove the Wavefront integration, please remove the `wavefront` user-provided service reference from [manifest.yml](./manifest.yml). \n\nOtherwise, generate a free wavefront token by running one of the apps, for example:\n\n```bash\ncd spring-petclinic-api-gateway\nmvn spring-boot:run\n```\n\nYou will see something like this in the logs:\n\n```\nA Wavefront account has been provisioned successfully and the API token has been saved to disk.\n\nTo share this account, make sure the following is added to your configuration:\n\n\tmanagement.metrics.export.wavefront.api-token=2e41f7cf-1111-2222-3333-7397a56113ca\n\tmanagement.metrics.export.wavefront.uri=https://wavefront.surf\n\nConnect to your Wavefront dashboard using this one-time use link:\nhttps://wavefront.surf/us/AAA4s5f8xJ9yD\n\n```\n\nYou free account has now been created.\n\nCreate a user-provided service for Wavefront using the data above. For example:\n\n```\ncf cups -p '{\"uri\": \"https://wavefront.surf\", \"api-token\": \"2e41f7cf-1111-2222-3333-7397a56113ca\", \"application-name\": \"spring-petclinic-cloudfoundry\", \"fremium\": \"true\"}' wavefront\n```\nIf your operator deployed the wavefront proxy in your Cloud Foundry environment, point the URI to the proxy instead. You can obtain the value of the IP and port by creating a service key of the wavefront proxy and viewing the resulting JSON file. \n\nContine with creating the services and deploying the application's microservices. A sample is available at `scripts/deployToCloudFoundry.sh`. Note that some of the services' plans may be different in your environment, so please review before executing. For example, you want want to fork the [spring-petclinic-cloud-config](https://github.com/spring-petclinic/spring-petclinic-cloud-config.git) repository if you want to make changes to the configuration.\n\n```\necho \"Creating Required Services...\"\n{\n  cf create-service -c '{ \"git\": { \"uri\": \"https://github.com/spring-petclinic/spring-petclinic-cloud-config.git\", \"periodic\": true }, \"count\": 3 }' p.config-server standard config \u0026\n  cf create-service p.service-registry standard registry \u0026 \n  cf create-service p.mysql db-small customers-db \u0026\n  cf create-service p.mysql db-small vets-db \u0026\n  cf create-service p.mysql db-small visits-db \u0026\n  sleep 5\n} \u0026\u003e /dev/null\nuntil [ `cf service config | grep -c \"succeeded\"` -ge 1  ] \u0026\u0026 [ `cf service registry | grep -c \"succeeded\"` -ge 1  ] \u0026\u0026 [ `cf service customers-db | grep -c \"succeeded\"` -ge 1  ] \u0026\u0026 [ `cf service vets-db | grep -c \"succeeded\"` -ge 1  ] \u0026\u0026 [ `cf service visits-db | grep -c \"succeeded\"` -ge 1  ]\ndo\n  echo -n \".\"\ndone\n\nmvn clean package -Pcloud\ncf push --no-start\n\ncf add-network-policy api-gateway --destination-app vets-service --protocol tcp --port 8080\ncf add-network-policy api-gateway --destination-app customers-service --protocol tcp --port 8080\ncf add-network-policy api-gateway --destination-app visits-service --protocol tcp --port 8080\n\ncf start vets-service \u0026 cf start visits-service \u0026 cf start customers-service \u0026 cf start api-gateway \u0026\n```\n\nYou can now access your application by querying the route for the `api-gateway`:\n\n```\n✗ cf apps\nGetting apps in org pet-clinic / space pet-clinic as user@email.com...\nOK\n\nname                requested state   instances   memory   disk   urls\napi-gateway         started           1/1         1G       1G     api-gateway.apps.mysite.com\ncustomers-service   started           1/1         1G       1G     customers-service.apps.internal\nvets-service        started           1/1         1G       1G     vets-service.apps.internal\nvisits-service      started           1/1         1G       1G     visits-service.apps.internal\n\n```\n\nAccess your route (like `api-gateway.apps.mysite.com` above) to see the application.\n\nAccess the one-time URL you received when bootstraping Wavefront to see Zipkin traces and other monitoring of your microservices:\n\n![Wavefront dashboard screen](./docs/wavefront-summary.png)\n\nSince we've included `brave.mysql8` in our `pom.xml`, the traces even show the various DB queries traces:\n\n![Wavefront dashboard screen](./docs/wavefront-traces.png)\n\n\n\n## Compiling and pushing to Kubernetes\n\nThis get a little bit more complicated when deploying to Kubernetes, since we need to manage Docker images, exposing services and more yaml. But we can pull through!\n\n### Choose your Docker registry\n\nYou need to define your target Docker registry. Make sure you're already logged in by running `docker login \u003cendpoint\u003e` or `docker login` if you're just targeting Docker hub.\n\nSetup an env variable to target your Docker registry. If you're targeting Docker hub, simple provide your username, for example:\n\n```bash\nexport REPOSITORY_PREFIX=odedia\n```\n\nFor other Docker registries, provide the full URL to your repository, for example:\n\n```bash\nexport REPOSITORY_PREFIX=harbor.myregistry.com/demo\n```\n\nOne of the neat features in Spring Boot 2.3 is that it can leverage [Cloud Native Buildpacks](https://buildpacks.io) and [Paketo Buildpacks](https://paketo.io) to build production-ready images for us. Since we also configured the `spring-boot-maven-plugin` to use `layers`, we'll get optimized layering of the various components that build our Spring Boot app for optimal image caching. What this means in practice is that if we simple change a line of code in our app, it would only require us to push the layer containing our code and not the entire uber jar. To build all images and pushing them to your registry, run:\n\n```bash\nmvn spring-boot:build-image -Pk8s -DREPOSITORY_PREFIX=${REPOSITORY_PREFIX} \u0026\u0026 ./scripts/pushImages.sh\n```\n\nSince these are standalone microservices, you can also `cd` into any of the project folders and build it indivitually (as well as push it to the registry).\n\nYou should now have all your images in your Docker registry. It might be good to make sure you can see them available.\n\nMake sure you're targeting your Kubernetes cluster.\n\nDocker images for kubernetes have been published into DockerHub in the [springcommunity](https://hub.docker.com/u/springcommunity)\norganization. You can pull an image:\n```\ndocker pull springcommunity/spring-petclinic-cloud-discovery-service\n```\n\n### Setting things up in Kubernetes\n\nCreate the `spring-petclinic` namespace for Spring petclinic:\n\n```bash\nkubectl apply -f k8s/init-namespace/ \n```\n\nCreate a Kubernetes secret to store the URL and API Token of Wavefront (replace values with your own real ones):\n\n```bash\nkubectl create secret generic wavefront -n spring-petclinic --from-literal=wavefront-url=https://wavefront.surf --from-literal=wavefront-api-token=2e41f7cf-1111-2222-3333-7397a56113ca\n```\n\nCreate the Wavefront proxy pod, and the various Kubernetes services that will be used later on by our deployments:\n\n```bash\nkubectl apply -f k8s/init-services\n```\n\nVerify the services are available:\n\n```bash\n✗ kubectl get svc -n spring-petclinic\nNAME                TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)             AGE\napi-gateway         LoadBalancer   10.7.250.24    \u003cpending\u003e     80:32675/TCP        36s\ncustomers-service   ClusterIP      10.7.245.64    \u003cnone\u003e        8080/TCP            36s\nvets-service        ClusterIP      10.7.245.150   \u003cnone\u003e        8080/TCP            36s\nvisits-service      ClusterIP      10.7.251.227   \u003cnone\u003e        8080/TCP            35s\nwavefront-proxy     ClusterIP      10.7.253.85    \u003cnone\u003e        2878/TCP,9411/TCP   37s\n```\n\nVerify the wavefront proxy is running:\n\n```bash\n✗ kubectl get pods -n spring-petclinic\nNAME                              READY   STATUS    RESTARTS   AGE\nwavefront-proxy-dfbd4b695-fdd6t   1/1     Running   0          36s\n\n```\n\n### Settings up databases with helm\n\nWe'll now need to deploy our databases. For that, we'll use helm. You'll need helm 3 and above since we're not using Tiller in this deployment.\n\nMake sure you have a single `default` StorageClass in your Kubernetes cluster:\n\n```bash\n✗ kubectl get sc\nNAME                 PROVISIONER            AGE\nstandard (default)   kubernetes.io/gce-pd   6h11m\n\n```\n\nDeploy the databases:\n\n```bash\nhelm repo add bitnami https://charts.bitnami.com/bitnami\nhelm repo update\nhelm install vets-db-mysql bitnami/mysql --namespace spring-petclinic --version 8.8.8 --set auth.database=service_instance_db\nhelm install visits-db-mysql bitnami/mysql --namespace spring-petclinic  --version 8.8.8 --set auth.database=service_instance_db\nhelm install customers-db-mysql bitnami/mysql --namespace spring-petclinic  --version 8.8.8 --set auth.database=service_instance_db\n```\n\n### Deploying the application\n\nOur deployment YAMLs have a placeholder called `REPOSITORY_PREFIX` so we'll be able to deploy the images from any Docker registry. Sadly, Kubernetes doesn't support environment variables in the YAML descriptors. We have a small script to do it for us and run our deployments:\n\n```bash\n./scripts/deployToKubernetes.sh\n```\n\nVerify the pods are deployed:\n\n```bash\n✗ kubectl get pods -n spring-petclinic \nNAME                                 READY   STATUS    RESTARTS   AGE\napi-gateway-585fff448f-q45jc         1/1     Running   0          4m20s\ncustomers-db-mysql-0                 1/1     Running   0          11m\ncustomers-service-5d7d686654-kpcmx   1/1     Running   0          4m19s\nvets-db-mysql-0                      1/1     Running   0          11m\nvets-service-85cb8677df-l5xpj        1/1     Running   0          4m2s\nvisits-db-mysql-0                    1/1     Running   0          11m\nvisits-service-654fffbcc7-zj2jw      1/1     Running   0          4m2s\nwavefront-proxy-dfbd4b695-fdd6t      1/1     Running   0          14m\n```\n\nGet the `EXTERNAL-IP` of the API Gateway:\n\n```bash\n✗ kubectl get svc -n spring-petclinic api-gateway \nNAME          TYPE           CLUSTER-IP    EXTERNAL-IP      PORT(S)        AGE\napi-gateway   LoadBalancer   10.7.250.24   34.1.2.22   80:32675/TCP   18m\n```\n\nYou can now browse to that IP in your browser and see the application running.\n\nYou should also see monitoring and traces from Wavefront under the application name `spring-petclinic-k8s`:\n\n![Wavefront dashboard screen](./docs/wavefront-k8s.png)\n\n\n\n\n\n## Starting services locally without Docker\n\nEvery microservice is a Spring Boot application and can be started locally using IDE \nor `../mvnw spring-boot:run -Plocal` command.\nRemember to enable the `local` Maven profile.\n\nPlease note that supporting services (Config and Discovery Server) must be started before any other application (Customers, Vets, Visits and API).\nStartup of Tracing server, Admin server, Grafana and Prometheus is optional.\nIf everything goes well, you can access the following services at given location:\n\n* Discovery Server - http://localhost:8761\n* Config Server - http://localhost:8888\n* AngularJS frontend (API Gateway) - http://localhost:8080\n* Customers, Vets and Visits Services - random port, check Eureka Dashboard \n* Tracing Server (Zipkin) - http://localhost:9411/zipkin/ (we use [openzipkin](https://github.com/openzipkin/zipkin/tree/master/zipkin-server))\n* Admin Server (Spring Boot Admin) - http://localhost:9090\n* Grafana Dashboards - http://localhost:3000\n* Prometheus - http://localhost:9091\n\nYou can tell Config Server to use your local Git repository by using `native` Spring profile and setting\n`GIT_REPO` environment variable, for example:\n`-Dspring.profiles.active=native -DGIT_REPO=/projects/spring-petclinic-microservices-config`\n\n## Starting services locally with docker-compose\n\nIn order to start entire infrastructure using Docker, you have to build images by executing `./mvnw clean install -P buildDocker` \nfrom a project root. Once images are ready, you can start them with a single command\n`docker-compose up`. Containers startup order is coordinated with [`dockerize` script](https://github.com/jwilder/dockerize). \nAfter starting services it takes a while for API Gateway to be in sync with service registry,\nso don't be scared of initial Spring Cloud Gateway timeouts. You can track services availability using Eureka dashboard\navailable by default at http://localhost:8761.\n\nThe `master` branch uses an  Alpine linux  with JRE 8 as Docker base. You will find a Java 11 version in the `release/java11` branch.\n\n*NOTE: Under MacOSX or Windows, make sure that the Docker VM has enough memory to run the microservices. The default settings\nare usually not enough and make the `docker-compose up` painfully slow.*\n\n\n## In case you find a bug/suggested improvement for Spring Petclinic Microservices\n\nOur issue tracker is available here: https://github.com/spring-petclinic/spring-petclinic-cloud/issues\n\n## Database configuration\n\nIn its default configuration, Petclinic uses an in-memory database (HSQLDB) which gets populated at startup with data.\nA similar setup is provided for MySql in case a persistent database configuration is needed.\nDependency for Connector/J, the MySQL JDBC driver is already included in the `pom.xml` files.\n\n### Start a MySql database\n\nYou may start a MySql database with docker:\n\n```\ndocker run -e MYSQL_ROOT_PASSWORD=petclinic -e MYSQL_DATABASE=petclinic -p 3306:3306 mysql:5.7.8\n```\nor download and install the MySQL database (e.g., MySQL Community Server 5.7 GA), which can be found here: https://dev.mysql.com/downloads/\n\n### Use the Spring 'mysql' profile\n\nTo use a MySQL database, you have to start 3 microservices (`visits-service`, `customers-service` and `vets-services`)\nwith the `mysql` Spring profile. Add the `--spring.profiles.active=mysql` as programm argument.\n\nBy default, at startup, database schema will be created and data will be populated.\nYou may also manually create the PetClinic database and data by executing the `\"db/mysql/{schema,data}.sql\"` scripts of each 3 microservices. \nIn the `application.yml` of the [Configuration repository], set the `initialization-mode` to `never`.\n\nIf you are running the microservices with Docker, you have to add the `mysql` profile into the (Dockerfile)[docker/Dockerfile]:\n```\nENV SPRING_PROFILES_ACTIVE docker,mysql\n```\nIn the `mysql section` of the `application.yml` from the [Configuration repository], you have to change \nthe host and port of your MySQL JDBC connection string. \n\n## Custom metrics monitoring\n\nGrafana and Prometheus are included in the `docker-compose.yml` configuration, and the public facing applications\nhave been instrumented with [MicroMeter](https://micrometer.io) to collect JVM and custom business metrics.\n\nA JMeter load testing script is available to stress the application and generate metrics: [petclinic_test_plan.jmx](spring-petclinic-api-gateway/src/test/jmeter/petclinic_test_plan.jmx)\n\n![Grafana metrics dashboard](docs/grafana-custom-metrics-dashboard.png)\n\n### Using Prometheus\n\n* Prometheus can be accessed from your local machine at http://localhost:9091\n\n### Using Grafana with Prometheus\n\n* An anonymous access and a Prometheus datasource are setup.\n* A `Spring Petclinic Metrics` Dashboard is available at the URL http://localhost:3000/d/69JXeR0iw/spring-petclinic-metrics.\nYou will find the JSON configuration file here: [docker/grafana/dashboards/grafana-petclinic-dashboard.json]().\n* You may create your own dashboard or import the [Micrometer/SpringBoot dashboard](https://grafana.com/dashboards/4701) via the Import Dashboard menu item.\nThe id for this dashboard is `4701`.\n\n### Custom metrics\nSpring Boot registers a lot number of core metrics: JVM, CPU, Tomcat, Logback... \nThe Spring Boot auto-configuration enables the instrumentation of requests handled by Spring MVC.\nAll those three REST controllers `OwnerResource`, `PetResource` and `VisitResource` have been instrumented by the `@Timed` Micrometer annotation at class level.\n\n* `customers-service` application has the following custom metrics enabled:\n  * @Timed: `petclinic.owner`\n  * @Timed: `petclinic.pet`\n* `visits-service` application has the following custom metrics enabled:\n  * @Timed: `petclinic.visit`\n\n## Looking for something in particular?\n\n| Spring Cloud components         | Resources  |\n|---------------------------------|------------|\n| Configuration server            | [Config server properties](spring-petclinic-config-server/src/main/resources/application.yml) and [Configuration repository] |\n| Service Discovery               | [Eureka server](spring-petclinic-discovery-server) and [Service discovery client](spring-petclinic-vets-service/src/main/java/org/springframework/samples/petclinic/vets/VetsServiceApplication.java) |\n| API Gateway                     | [Spring Cloud Gateway starter](spring-petclinic-api-gateway/pom.xml) and [Routing configuration](/spring-petclinic-api-gateway/src/main/resources/application.yml) |\n| Docker Compose                  | [Spring Boot with Docker guide](https://spring.io/guides/gs/spring-boot-docker/) and [docker-compose file](docker-compose.yml) |\n| Circuit Breaker                 | [Resilience4j fallback method](spring-petclinic-api-gateway/src/main/java/org/springframework/samples/petclinic/api/boundary/web/ApiGatewayController.java)  |\n| Grafana / Prometheus Monitoring | [Micrometer implementation](https://micrometer.io/), [Spring Boot Actuator Production Ready Metrics] |\n\n Front-end module  | Files |\n|-------------------|-------|\n| Node and NPM      | [The frontend-maven-plugin plugin downloads/installs Node and NPM locally then runs Bower and Gulp](spring-petclinic-ui/pom.xml)  |\n| Bower             | [JavaScript libraries are defined by the manifest file bower.json](spring-petclinic-ui/bower.json)  |\n| Gulp              | [Tasks automated by Gulp: minify CSS and JS, generate CSS from LESS, copy other static resources](spring-petclinic-ui/gulpfile.js)  |\n| Angular JS        | [app.js, controllers and templates](spring-petclinic-ui/src/scripts/)  |\n\n\n## Interesting Spring Petclinic forks\n\nThe Spring Petclinic master branch in the main [spring-projects](https://github.com/spring-projects/spring-petclinic)\nGitHub org is the \"canonical\" implementation, currently based on Spring Boot and Thymeleaf.\n\nThis [spring-petclinic-cloud](https://github.com/spring-petclinic/spring-petclinic-cloud/) project is one of the [several forks](https://spring-petclinic.github.io/docs/forks.html) \nhosted in a special GitHub org: [spring-petclinic](https://github.com/spring-petclinic).\nIf you have a special interest in a different technology stack\nthat could be used to implement the Pet Clinic then please join the community there.\n\n\n# Contributing\n\nThe [issue tracker](https://github.com/spring-petclinic/spring-petclinic-microservices/issues) is the preferred channel for bug reports, features requests and submitting pull requests.\n\nFor pull requests, editor preferences are available in the [editor config](.editorconfig) for easy use in common text editors. Read more and download plugins at \u003chttp://editorconfig.org\u003e.\n\n\n[Configuration repository]: https://github.com/spring-petclinic/spring-petclinic-microservices-config\n[Spring Boot Actuator Production Ready Metrics]: https://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-metrics.html\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspring-petclinic%2Fspring-petclinic-cloud","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fspring-petclinic%2Fspring-petclinic-cloud","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspring-petclinic%2Fspring-petclinic-cloud/lists"}