microservices-demo VS microservices-demo

As an inbetween beginner and advanced you can look at this project - https://microservices-demo.github.io/ its more practical and again uses Python.

I'm new to kubernetes world. I got sample kubernetes deployments (like sock-shop) working end-to-end without any issues. I tried NodePort to access the service but instead of running it on a different port I need to run it exact port 80 on the host. I tried many ingress solutions but didn't work.

Here's an example app that fits all of the criteria above. Can be used as a good reference point. https://github.com/microservices-demo/microservices-demo

1) Deploy the Sock Shop app in our K8s cluster. While we’ll use Sock Shop as our example application, you can deploy your own app to your cluster and still follow along. 2) Deploy APIClarity in our K8s cluster and configure monitoring 3) Observe API traffic on the APIClarity dashboard 4) Review and create an API specification and view the generated OpenAPI spec in Swagger format. 5) Identify deviations from an API spec along with usage of shadow and zombie APIs. 6) View and filter API events

Depending on what you want there is Microservice demo from Google or Sock Shop from Weaveworks.

There are sample application that you could deploy, for example https://github.com/microservices-demo/microservices-demo

You can check https://github.com/GoogleCloudPlatform/microservices-demo for Kubernetes show-casing

Skyramp provides a sample project, sample-microservices, which serves as an excellent starting point for demonstrating testing and mocking with a full-featured distributed application. The application is based on Google's Online Boutique repo, which is an e-commerce store consisting of 11 different microservices. The docker-compose-demo branch referenced above showcases how Skyramp can be seamlessly integrated with Docker Compose for testing microservices with no local setup required. You can also clone the repository and explore the structure of the microservices setup for your own purposes.

Our starting point is the hot-code-reload-demo branch in Skyramp's letsramp/sample-microservices GitHub repo. You can use your browser to navigate to the correct branch in the repo here. The sample-microservices repo contains a demo project based on GCP's Online Boutique with added support for REST and Thrift APIs. This sample e-commerce application is perfect for demonstrating cloud-native development and testing, including debugging with Hot Code Reload with Skyramp.

This blog features the Skyramp fork of Google’s popular cloud-native microservices demo app, Online Boutique. Online Boutique is a web-based e-commerce app containing microservices that mimic real-world services, such as a product catalog, shopping cart, ad service, recommendation service, payment service, and others. The services use gRPC APIs by default, but Skyramp has also added support for REST and Thrift APIs.

I'm planning to host this application: Google Microservices Demo (It's an online shop)

Well, what is considered "real" data here? Why couldn't you simply set up a managed k8s cluster with some prometheus monitoring and run the microservices-demo on it. There is even a synthetic load generator. You could purposefully add in specific kinds of faults into the working system, ones that are supported in metasploit so you can automate intrusions. Consider some goals for gaining access like: exfiltration, denial of service, ransomware. Then consider how you might detect such attacks purely from what you can read out of the prometheus time series data (eg. high egress traffic plus high req/s to redis might mean an exfiltration).

The microservices source code repository for this project is from this link; google-microservices-demo, containing 11 services we will deploy with this demo. Also, from the same repo, it was illustrated and visualized how these services are connected to each other including a 3rd party service for database - redis. Among the services, Frontend serves as an entrypoint for all the services receiving external requests from the browser. Meanwhile, the load generator deployment is optional, so in this demo we wouldn't bother deploying it.

This demo repo might be a good starting point: https://github.com/GoogleCloudPlatform/microservices-demo

OpenAPI and possibly developing reusable, versioned client libraries could help, but it's a major undertaking that gRPC makes redundant. I'd be tempted to use grpc-gateway even if I had to implement a REST API. Try looking into buf and monorepo structures for proto management, e.g. something like GoogleCloudPlatform/microservices-demo. For more thorough proto and grpc-gateway definition examples, see googleapis/googleapis.

I also just discovered Google Cloud's microservices-demo repository, which has some samples of how to set up otel observability and GCP-specific Go profiling on GCP. I wish I'd found it before setting up otel myself.