How instana/robot-shop works
Project type and purpose
• This is a full-stack, sample microservice application (“Stan’s Robot Shop”) intended as a sandbox for learning containerized orchestration (Docker Compose, Swarm, DCOS, Kubernetes/Helm, OpenShift) plus distributed tracing and monitoring (Instana).
• It consists of multiple language-specific microservices (NodeJS, Java/Spring Boot, Python/Flask, Go, PHP), a static/AngularJS web UI served by Nginx, message-driven integration via RabbitMQ, and persistence layers (MongoDB, MySQL, Redis).
File structure
• Top-level microservice directories: cart (Node), catalogue (Node), dispatch (Go), payment (Python), ratings (PHP/Apache), shipping (Java/Spring Boot), user (Node), web (Nginx + static front end).
• Persistence directories: mongo, mysql; each provides Dockerfiles and init scripts.
• Cross-cutting concerns: fluentd (logging aggregator), load-gen (Python/Locust load tester).
• Orchestration/deployment manifests under: docker-compose.yaml(s), Swarm/, DCOS/, K8s/ (with Istio gateway + Helm chart), OpenShift/.
• Env/config files: .env, Helm values.yaml, Kubernetes YAMLs, DCOS manifests, service startup scripts.
README for additional insights
• Stack: NodeJS/Express, Spring Boot, Flask, Golang, PHP + MySQL, MongoDB, Redis, RabbitMQ, Nginx, AngularJS.
• Monitoring/tracing via Instana agents built into each service.
• Prometheus metrics exposed on cart and payment services.
• Load-generation (Locust) separate, optional.
• Multiple deployment targets: local Docker Compose, Swarm, DCOS, Kubernetes (Helm/OpenShift).
Elements
• Clear, human-readable labels for each service component and database
• Cross-cutting (monitoring/logging agents in a different style)
• Deployment context overlays: containers/pods, sidecar proxies (Istio), namespaces