Skip to main content

Developers

Spider is of great help for developers!

Use cases​

  • Check integration requests from components under development and services
  • Check datastore requests made by ORM or others abstraction libraries
  • Check effect of service calls in the fan out between services
  • Debug automatic tests by identifying and replaying requests
  • Analyse parallel processing test cases or issues
  • Check performance of the call flow
  • Perform reverse engineering of a service / component

Tips​

  • Attach remotely Whisperers with Controller to the Kubernetes workload under dev 💡
  • Filter on the services you're working on
  • Limit to specific timestamp (zoom on timeline) for faster queries
  • Use sequence diagrams for parallel processing and fan out studies

To capture real time service calls​

  • Hide the map for faster queries, use the dashboard
  • Filter on your 'client' identification
  • Queries sent by your component / test are visible in 10s in Spider
tip

This can greatly reduce the need for debug / trace logs and tooling.
This replaces 'guessing' by 'watching'.

To capture communications to datastores​

  • Attach Whisperers to statefulsets
  • Use TCP capture, with Packet storing active

To check performance of the service​

  • Active packet storing to check how data is transmitted from the service (by group of packets or all at once)
  • Check sequence diagram of the service outbounds calls to check service inner working times