• Microservices Meetup - Open Tracing

    Last week at the Microservices Meetup at Signal.AI who gave a talk on open tracing!

    Firstly, what is Open Tracing?

    Microservices is a recent trend in Computer Science that involves a multitude of smaller pieces of the overall Application Architecture that work together to create the Software rather than a singular Monolithic Application. This allows for far faster/independent deployment that are more easily testable.
    This has its own problems, not least of which is the fact you now have numerous systems that have to speak to each other and this can cause problems working out what is actually going on. Open Tracing comes in as a system to describe and analyse transactions that are occurring on a Microservice to better see how things are working (or not!) together and most importantly standardises the instrumentation of the process so that it can continue working as you scale.

    Signal uses Tracing data to form their development strategy going forward, and to capitalise on this sticks to Tech's that work very well with Tracing such as Clojure/Kotlin and Python and avoids AWS where possible as it can run into IP and Port issues with Open Tracing.

    Are you using Traces in your Tech Stack?


    Name:  Microservices-min.JPG
Views: 14
Size:  1.00 MB
    1
  • Last week at the Microservices Meetup at Signal.AI who gave a talk on open tracing!

    Firstly, what is Open Tracing?

    Microservices is a recent trend in Computer Science that involves a multitude of smaller pieces of the overall Application Architecture that work together to create the Software rather than a singular Monolithic Application. This allows for far faster/independent deployment that are more easily testable.
    This has its own problems, not least of which is the fact you now have numerous systems that have to speak to each other and this can cause problems working out what is actually going on. Open Tracing comes in as a system to describe and analyse transactions that are occurring on a Microservice to better see how things are working (or not!) together and most importantly standardises the instrumentation of the process so that it can continue working as you scale.

    Signal uses Tracing data to form their development strategy going forward, and to capitalise on this sticks to Tech's that work very well with Tracing such as Clojure/Kotlin and Python and avoids AWS where possible as it can run into IP and Port issues with Open Tracing.

    Are you using Traces in your Tech Stack?


    Name:  Microservices-min.JPG
Views: 14
Size:  1.00 MB