kandi background
Explore Kits

microservices-demo | Sample cloud-native application | GCP library

 by   GoogleCloudPlatform Python Version: v0.3.6 License: Apache-2.0

 by   GoogleCloudPlatform Python Version: v0.3.6 License: Apache-2.0

Download this library from

kandi X-RAY | microservices-demo Summary

microservices-demo is a Python library typically used in Cloud, GCP applications. microservices-demo has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. However microservices-demo build file is not available. You can download it from GitHub.
⚠ ATTENTION: Apache Log4j 2 advisory. Due to vulnerabilities present in earlier versions of Log4j 2, we have taken down all affected container images. We highly recommend all demos and forks to now use images from releases >= v0.3.4. Online Boutique is a cloud-native microservices demo application. Online Boutique consists of a 10-tier microservices application. The application is a web-based e-commerce app where users can browse items, add them to the cart, and purchase them. Google uses this application to demonstrate use of technologies like Kubernetes/GKE, Istio, Stackdriver, gRPC and OpenCensus. This application works on any Kubernetes cluster, as well as Google Kubernetes Engine. It’s easy to deploy with little to no configuration.
Support
Support
Quality
Quality
Security
Security
License
License
Reuse
Reuse

kandi-support Support

  • microservices-demo has a medium active ecosystem.
  • It has 12028 star(s) with 3609 fork(s). There are 236 watchers for this library.
  • There were 4 major release(s) in the last 12 months.
  • There are 35 open issues and 238 have been closed. On average issues are closed in 48 days. There are 7 open pull requests and 0 closed requests.
  • It has a neutral sentiment in the developer community.
  • The latest version of microservices-demo is v0.3.6
microservices-demo Support
Best in #GCP
Average in #GCP
microservices-demo Support
Best in #GCP
Average in #GCP

quality kandi Quality

  • microservices-demo has 0 bugs and 0 code smells.
microservices-demo Quality
Best in #GCP
Average in #GCP
microservices-demo Quality
Best in #GCP
Average in #GCP

securitySecurity

  • microservices-demo has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
  • microservices-demo code analysis shows 0 unresolved vulnerabilities.
  • There are 0 security hotspots that need review.
microservices-demo Security
Best in #GCP
Average in #GCP
microservices-demo Security
Best in #GCP
Average in #GCP

license License

  • microservices-demo is licensed under the Apache-2.0 License. This license is Permissive.
  • Permissive licenses have the least restrictions, and you can use them in most projects.
microservices-demo License
Best in #GCP
Average in #GCP
microservices-demo License
Best in #GCP
Average in #GCP

buildReuse

  • microservices-demo releases are available to install and integrate.
  • microservices-demo has no build file. You will be need to create the build yourself to build the component from source.
  • Installation instructions, examples and code snippets are available.
  • microservices-demo saves you 8010 person hours of effort in developing the same functionality from scratch.
  • It has 16667 lines of code, 1864 functions and 60 files.
  • It has medium code complexity. Code complexity directly impacts maintainability of the code.
microservices-demo Reuse
Best in #GCP
Average in #GCP
microservices-demo Reuse
Best in #GCP
Average in #GCP
Top functions reviewed by kandi - BETA

kandi has reviewed microservices-demo and discovered the below as its top functions. This is intended to give you an instant insight into microservices-demo implemented functionality, and help decide if they suit your requirements.

  • Sends an order confirmation email
    • Sends a confirmation email
  • Start the server
    • Adds an email service servicer to the given server
  • Checkout a cart
    • Add product to cart
  • Set index
    • Index server
  • Adds recommendations service servicer to server
    • Get a JSON logger

      Get all kandi verified functions for this library.

      Get all kandi verified functions for this library.

      microservices-demo Key Features

      Kubernetes/GKE: The app is designed to run on Kubernetes (both locally on "Docker for Desktop", as well as on the cloud with GKE).

      gRPC: Microservices use a high volume of gRPC calls to communicate to each other.

      Istio: Application works on Istio service mesh.

      OpenCensus Tracing: Most services are instrumented using OpenCensus trace interceptors for gRPC/HTTP.

      Cloud Operations (Stackdriver): Many services are instrumented with Profiling, Tracing and Debugging. In addition to these, using Istio enables features like Request/Response Metrics and Context Graph out of the box. When it is running out of Google Cloud, this code path remains inactive.

      Skaffold: Application is deployed to Kubernetes with a single command using Skaffold.

      Synthetic Load Generation: The application demo comes with a background job that creates realistic usage patterns on the website using Locust load generator.

      Quickstart (GKE)

      copy iconCopydownload iconDownload
      PROJECT_ID="<your-project-id>"
      gcloud services enable container.googleapis.com --project ${PROJECT_ID}
      gcloud services enable monitoring.googleapis.com \
          cloudtrace.googleapis.com \
          clouddebugger.googleapis.com \
          cloudprofiler.googleapis.com \
          --project ${PROJECT_ID}
      

      Reference to undeclared resource in Terraform

      copy iconCopydownload iconDownload
      resource "aws_key_pair" "microservcies-demo-key" {
      

      Can't use a method from another file in same package

      copy iconCopydownload iconDownload
      server := FrontendServer{}
      
      server := FrontendServer{
          Router: mux.NewRouter(),
      }
      
      server := FrontendServer{}
      
      server := FrontendServer{
          Router: mux.NewRouter(),
      }
      

      Atleast one invalid signature was encountered

      copy iconCopydownload iconDownload
      # docker run -it debian:buster /bin/date
      Sun Nov 15 11:30:44 UTC 2020
      # docker run -it debian:sid /bin/date 
      Thu Jan  1 00:00:00 UTC 1970
      
      $ docker image prune 
      $ docker container prune 
      
      $ docker image prune -a 
      
      $ docker image prune -a --filter "until=24h"
      
      $ docker image prune 
      $ docker container prune 
      
      $ docker image prune -a 
      
      $ docker image prune -a --filter "until=24h"
      
      $ docker image prune 
      $ docker container prune 
      
      $ docker image prune -a 
      
      $ docker image prune -a --filter "until=24h"
      

      How to edit this Deployment Yaml to have write permission in container

      copy iconCopydownload iconDownload
      securityContext:
        runAsUser: 0
      
      USER root
      

      Terraform output from module source not found in main output

      copy iconCopydownload iconDownload
      output "api-gateway-codedeploy-app-name" {
        value = api-gateway-codedeploy.app-name
      }
      
      output "api-gateway-codedeploy-app-name" {
         value = module.api-gateway-codedeploy.app-name
      }
      
      output "api-gateway-codedeploy-app-name" {
        value = api-gateway-codedeploy.app-name
      }
      
      output "api-gateway-codedeploy-app-name" {
         value = module.api-gateway-codedeploy.app-name
      }
      

      Community Discussions

      Trending Discussions on microservices-demo
      • Go service name change for linkerd
      • Eclipse STS - Out of memory
      • Reference to undeclared resource in Terraform
      • @SpringBootApplication Not found error coming on module
      • Can't use a method from another file in same package
      • How to resolve DNS lookup error when trying to run example microservice application using minikube
      • Atleast one invalid signature was encountered
      • Online Boutique Extensions
      • Readiness probe failed: timeout: failed to connect service ":8080" within 1s
      • How I use one YAML to deploy two servers where one depends on the other one in Kubernetes
      Trending Discussions on microservices-demo

      QUESTION

      Go service name change for linkerd

      Asked 2021-Nov-16 at 17:19

      I have configured linkerd with 2 clusters in GKE (west and east cluster) for multicluster purpose. I used this demo app provided by google https://github.com/GoogleCloudPlatform/microservices-demo

      First I did it with Istio and everything worked out fine, but with linkerd its different. As expected the exported service from east to west cluster with get the cluster name appended to the service. eg in west cluster ,you will get currencyservice-east.

      The problem I think I am having is that the frontend in the west cluster keeps sending request to currencyservice instead of currencyservice-east.

      I didn't have this problem in Istio because Istio used the same service name across clusters. I am not a GO programmer, but I have googled my life to find out where the service name was defined in the frontend source code to change it but I have not succeeded.

      another alternative will be for linkerd to maintain the service name while exporting it.

      please guys help me.

      ANSWER

      Answered 2021-Nov-16 at 17:19

      You can use a TrafficSplit on the source cluster to direct calls to currentservice to currentservice-east.

      Source https://stackoverflow.com/questions/69976054

      Community Discussions, Code Snippets contain sources that include Stack Exchange Network

      Vulnerabilities

      No vulnerabilities reported

      Install microservices-demo

      After a few minutes, you should see:. Note- you may see <pending> while GCP provisions the load balancer. If this happens, wait a few minutes and re-run the command.
      Create a Google Cloud Platform project or use an existing project. Set the PROJECT_ID environment variable and ensure the Google Kubernetes Engine and Cloud Operations APIs are enabled.
      Clone this repository.
      Create a GKE cluster.
      GKE autopilot mode (see Autopilot overview to learn more):
      GKE Standard mode:
      Deploy the sample app to the cluster.
      Wait for the Pods to be ready.
      Access the web frontend in a browser using the frontend's EXTERNAL_IP.
      [Optional] Clean up:

      Support

      For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

      DOWNLOAD this Library from

      Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
      over 430 million Knowledge Items
      Find more libraries
      Reuse Solution Kits and Libraries Curated by Popular Use Cases
      Explore Kits

      Save this library and start creating your kit

      Explore Related Topics

      Share this Page

      share link
      Reuse Pre-built Kits with microservices-demo
      Consider Popular GCP Libraries
      Try Top Libraries by GoogleCloudPlatform
      Compare GCP Libraries with Highest Support
      Compare GCP Libraries with Highest Quality
      Compare GCP Libraries with Highest Security
      Compare GCP Libraries with Permissive License
      Compare GCP Libraries with Highest Reuse
      Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
      over 430 million Knowledge Items
      Find more libraries
      Reuse Solution Kits and Libraries Curated by Popular Use Cases
      Explore Kits

      Save this library and start creating your kit

      • © 2022 Open Weaver Inc.