Tes Engineering Blog

Musings of the Tes Engineering Team

BlogHow we workMeet the TeamOpen rolesWork with us

Posts tagged with "technology"

  1. An introduction to AWS Lambda

    19 February, 2020

    Phil, a Senior Engineer at Tes, gave a great introduction to AWS Lambdas during our weekly knowledge sharing session. These hour long sessions are meant for Tes Engineers only, but this session contained a lot of useful information that I'm sure is relevant for people outside of Tes as well. In his talk, Phil gives a brief introduction to AWS Lambdas and shows some use cases. He also goes into the…

  2. Testing in Production is not for free - a real life tale

    05 September, 2019

    Here's a real life tale of how we used Application Monitoring, Observability and Graceful Degradation to be able to ship fast but also catch and fix mistakes without letting our users down. In it we take a look at safe failure states and complementing metrics with supporting data and how we use them to solve real issues. Let me take you back to 6th June. Everything was fine and normal on Tes.com…

  3. Exceptional Alerts - Instrumenting and Observing Part 3

    20 June, 2019

    Observing what happens when your users interact with your software keep you from disaster, allowing your users to keep working and you to keep shipping. At Tes we capture what happens when our users interact with our services. We set expectations on outcomes. This means we know when our users can't reach their goals. It also means we can act fast to fix problems. In this blog post I'll show how…

  4. Enabling a secure culture in engineering: the SecEng Team

    03 May, 2019

    A sense of separation has sometimes existed between Security and Development, as though the two are not inherently connected. Security considerations have always fed into the way we work at Tes, but without the right connections it can be easy to end up viewing security as an impediment to speedy delivery or vice versa. We started a Security Engineering team ('SecEng' if you like) to bridge this…

  5. Slimmer micro-services with async-define

    05 April, 2019

    Before introducing async-define, I'd like to give some context to explain what problem it solves and why we have to deal with these kind of problems at Tes. micro-services integration One of the most important decisions we had to take when designing our micro-service architecture, is how to make micro-services work together. This is a particularly tricky choice, because you should choose a pattern…

  6. Aligning Divs and Devs: getting a consistent front-end

    22 August, 2018

    Imagine discovering your house had subtly changed every time you came home. The cupboard doors open different ways. The light-switches control different lights, and the hot and cold taps in your kitchen swap places. The inconsistency would be maddening – and the same goes for apps and websites. Creating a consistent UI keeps your users sane and orientated. For any product where there are multiple…

  7. Quick, clean commits with partial linting

    04 July, 2018

    Tired of your commits taking >10 seconds? Give this a bash. Linting is great, but no one likes slow commits! At Tes, we use to run code when the git hook triggers. Most often, we run so that we can catch linting errors before they're even committed. (We use ESLint for linting.) The problem is that, even when you're developing microservices, it could take quite a while to lint all the files in…

  8. Instrumenting and Observing Microservices Part 2: Are your microservices working together?

    12 February, 2018

    If you want to be confident that your users are able to achieve their goals using your service there's more to do than monitoring the health of individual microservices. You need assurance that your set of microservices are working well together, and when they aren't, you need the information necessary to fix any problems as soon as you can. This blog follows one Tes team's mission to better…

  9. Instrumenting and Observing Microservices Part 1: What do you expect from your microservice?

    03 November, 2017

    A friend of mine tells a great story of a team avoiding a great deal of grief. All of their system health checks were green, but the live graph of purchases dropped to zero and stayed there. Despite the many positive system indicators, the team were able to see they had a problem and were able able to react quickly to find and to fix it. It turned out that user purchases was a key indicator of…

© Tes Engineering Team 2020| All rights reserved
Follow @tes_engineering