Migrating a data intensive microservice from Python to Go

Migrating a data intensive microservice from Python to Go

As Uber is hyper-growing as a company so does our need for scalable and resilient systems. In this talk, I’m going to tell the story of how my team migrated from Python to Go, a microservice that processes millions of events every day. First, we are going to start with the rationale behind the migration. Then we are going to go over the Python and Go tech stacks that we use. Last but not least, I’m also going to share our approach for migrating the service while running in production, adding new features and making sure there are no regressions.

Eb44761e0fb3a5ec8e23ec28048dd7a5?s=128

Nikolay Stoitsev

June 10, 2019
Tweet

Transcript

  1. None
  2. None
  3. None
  4. None
  5. None
  6. None
  7. None
  8. None
  9. None
  10. None
  11. None
  12. Kafka Upstream Systems

  13. None
  14. None
  15. None
  16. None
  17. None
  18. None
  19. Kafka Upstream Systems

  20. None
  21. None
  22. None
  23. None
  24. None
  25. None
  26. Controller Mapper Service Entities External Services Database

  27. None
  28. None
  29. None
  30. None
  31. None
  32. None
  33. None
  34. None
  35. None
  36. None
  37. None
  38. None
  39. None
  40. None
  41. None
  42. None
  43. None
  44. None
  45. Upstream Systems

  46. Upstream Systems

  47. Upstream Systems

  48. None
  49. None
  50. None
  51. None
  52. Kafka Upstream Systems

  53. Kafka Upstream Systems

  54. Kafka Upstream Systems

  55. Kafka Upstream Systems

  56. Kafka Upstream Systems

  57. Kafka Upstream Systems Kafka

  58. None
  59. None
  60. None
  61. None
  62. None
  63. None
  64. None
  65. None
  66. None
  67. None
  68. None
  69. None
  70. None
  71. None
  72. None
  73. Proprietary © 2019 Uber Technologies, Inc. All rights reserved. No

    part of this document may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval systems, without permission in writing from Uber. This document is intended only for the use of the individual or entity to whom it is addressed and contains information that is privileged, confidential or otherwise exempt from disclosure under applicable law. All recipients of this document are notified that the information contained herein includes proprietary and confidential information of Uber, and recipient may not make use of, disseminate, or in any way disclose this document or any of the enclosed information to any person other than employees of addressee to the extent necessary for consultations with authorized personnel of Uber.