Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

devops.barcelona 2019 - Spartans don't like bad data

170 views

Published on

Presentation about how to built a service offering latency data to close neverending discussions. What are the most important thing to work on? I believe that building trust in the service is one of the main topics.

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

devops.barcelona 2019 - Spartans don't like bad data

  1. 1. Spartans don’t like bad data by Paco Orozco Jun 5th 2019
  2. 2. How many of you have seen it?
  3. 3. ● Since October 2017 ● Manager of 6 awesome engineers from 4 different nationalities ● Product owner of one of the most adopted service in the company. ○ YAMS is serving +10K requests/s ● Father of two outstanding daughters ● Hiker Engineering Manager @ Paco Orozco
  4. 4. About Adevinta Adevinta is a marketplace specialist. We are an international family of local digital brands. We help local marketplaces thrive in 16 countries around the world, through our global connections and networks of knowledge. 16 countries 800m Population footprint +1.1m Plastic tons saved
  5. 5. Adevinta around the world France Spain Brazil Italy Ireland Hungary Austria Colombia UK & Germany Chile Belarus Tunisia Dominican Republic Mexico Morocco
  6. 6. The problem
  7. 7. The Proof of Concept Tooling
  8. 8. First results, first success ● Which AWS regions are good enough for me? ● How much latency will I suffer on-boarding this service? ● Do I need any new region deployment to improve my service? ● How is my service delivering from X country? ● Am I improving latency of my service?
  9. 9. The RFC process
  10. 10. RFC output Buy vs build S2S only not user experience Focus in The Metrics Time to GET Errors HTTP and HTTPS DNS resolution time IPv4 Remote probes Docker Raspberry Pi Command line
  11. 11. some iterations later
  12. 12. Current implementation Tooling Metrics Exposer
  13. 13. Development flow Client testing (Yes! test everything) Build images (After every merge to master) Client deploy (balena.io for devices and docker + signed files in S3) Clients Targets
  14. 14. 15 probes across Adevinta
  15. 15. Success stories
  16. 16. The Yapo case
  17. 17. The future
  18. 18. PoC (AWSx6, bash, files) RFC (what & how to implement) Iterate as many times as needed Current (AWS+GCP+K 8s+API, golang, prometheus) Future (allow custom APIs as targets) To summarize ➔ Data needs to be relevant (what we need), accurate (we rely on it) & consistent (it’s comparable) ➔ Developing a service iteratively will give you always benefits ➔ The most important topic in this story is to achieve that our customers trust on the data Say what you are going to do and then do what you say! Communicate, communicate and communicate. Frequent, honest communication builds trust. Sell without selling out. Focus more on your core principles and customer loyalty than short term profits. Be transparent, authentic and willing to share your mistakes and faults.
  19. 19. Thank you! adevinta.com Paco Orozco @pakusland
  20. 20. adevinta.com Backup material
  21. 21. Clients Exposer
  22. 22. ● Latency Map client (bash) ● Latency Map client tests (bash) ● Latency Map client (go) ● Targets infrastructure ● Dummy test ● Latency Map dashboard ● AWS Service cost

×