条纹 VO挂经

上个月店面和VO 回馈地里。Recruiter很nice；基本都是面筋 但 integration 运气不好。。。经验/教训：
1. 遇到面筋题要装傻 但不能太傻 不然来不及写完。integration要至少做完两个part才算pass
2. debug做好懵逼的准备

您好！
本帖隐藏的内容需要积分高于 188 才可浏览
您当前积分为 0。
使用VIP即刻解锁阅读权限或查看其他获取积分的方式

游客，您好！
本帖隐藏的内容需要积分高于 188 才可浏览
您当前积分为 0。
VIP即刻解锁阅读权限 或 查看其他获取积分的方式
Unlock interview details and practice with AI
Curated Interview Questions from Top Companies

nk account:
4. HM

5. system design: metrics counter

1. ## Problem Statement
   
2. Imagine you work at a startup with many copies of many different services
   
3. running in production. You want to help your engineers keep track of metrics
   
4. like number of signups, number of requests, number of errors, etc. So you
   
5. introduce the concept of "counters". You build a `Track` library that ships
   
6. with every service, and anyone can call `Track.increment("some-metric")`
   
7. in their code to increment the `some-metric` counter.
   
8. 
   
9. This is really useful for quickly spotting anomalies. If you graph the number
   
10. of signups over time and it suddenly goes to zero, then we can assume that
    
11. something is not going well. This is mostly an operational tool (for example,
    
12. we’re not keeping track of precise dollar amounts for accounting or request
    
13. counts for rate limiting). Imagine we want to see the number of signups per
    
14. minute for the last 6 hours, or how many fraudulent cards were detected hourly
    
15. for the last day, or trends in a feature's adoption over the last few weeks.
    
16. 
    
17. Starting from just that interface, design everything that happens after
    
18. `Track.increment("some-metric")` gets called on a service, from what happens
    
19. inside the service to how the data is sent, collected, stored and accessed.
    
20. Think about how to support accessing the data, but don’t worry too much about
    
21. any actual graphing UI.
    
22. 
    
23. 
    
24. ## Sample System Diagram
    
25. ```
    
26. +---------------+
    
27. | login-service |--> Track.increment("new-signup")
    
28. |               |--> Track.increment("new-login")
    
29. +---------------+
    
30. 
    
31. +-----------------+
    
32. | payment-service |  
    
33. |                 |--> Track.increment("fraudulent-card")
    
34. +-----------------+
    
35. 
    
36. +--------------------+
    
37. | some-other-service |--> Track.increment("some-metric")
    
38. |                    |--> Track.increment("some-other-metric")
    
39. +--------------------+
    
40. 
    
41. ```

复制代码

请问你有没有问过他们是否需要做 back of envelop，然后他们说要做?

匿名者 发表于 2022-4-6 20:41
请问你有没有问过他们是否需要做 back of envelop，然后他们说要做?

请问back of envelop是什么意思？

pnhjd 发表于 2022-4-8 23:45
请问back of envelop是什么意思？

capacity calculations / back of the envelope calculations

感谢分享
继续努力！！！