Why did we choose to use GoLang

Transcript

1. Why did we choose to use goLang at Uniplaces
2. Who am I?
3. Peter Tilsen CTO
4. Contents Needs Challenge Solution Excursus Introduction
5. Introduction
6. Needs
7. Needs What do we strive for? Stability, Scaleability, Standards, Flows etc.
8. Needs What do we really strive for? Cost efficiency Time efficiency Growth Happiness
9. Needs How do we get there from the engineering side?
10. Challenge
11. Challenge Lets take a look at our stack
12. Stack: Frontend tier
13. Stack: Middle tier
14. Stack: Backend tier
15. Challenge Are we performant? Are we scaleable? So where’s the problem?
16. Challenge So why introducing a new technology?
17. Challenge Continue with php Introduce 1mio things: - Boss/Worker model (gearman, etc) - POSIX threads (pthreads) - php 7.x - More caching - jit compilation (hhvm) - Find leaks - etc.
18. Challenge “The ends justify the means” “Use the right tool for the job”
19. Challenge The job - Rapidly expandable APIs - Highly performant APIs - Granular decoupling of APIs - Big data transformation (ETL) - (Mobile development)
20. Challenge Why do I think that a new technology is the right tool?
21. Challenge Why not something else, but goLang? Java, Python Node.js c/c++
22. Solution
23. Solution Lets go for a new language
24. Introduction Factors to consider Popularity Language-domain match Availability of libraries Efficiency Expressiveness Project-size (Tool support)
25. Solution
26. Solution Why go? Simplicity Characteristics Standard library Tools ci capabilities Performance
27. Solution First occurrence 2007/2009 Developed at google Robert Griesemer, Rob Pike and Ken Thompson Compiled, statically typed C like language
28. Solution Simplicity - 25 keywords - Clear visibility definition - Easy dependency management - Packaging Steep learning curve
29. Solution Characteristics - Strictly typed - Structs - Arrays, Slices, Maps - Multiple return values - Interfaces - GoRoutines, Channels - Garbage collection
30. Solution Standard library (All) necessary functionality is part of standard lib - encoding/decoding (marshalling) - net http for servers - testing - io/util
31. Solution Tools - go fmt - go test (benchmark) - go doc - etc.
32. Solution ci Capabilities - deploy single artifact - cross platform compilation - no vm needed Increase development efficiency (short compilation time, fast cycle)
33. Solution Performance “Never trust a benchmark that you did not run yourself” No benchmarks
34. Solution Performance Concurrency What’s the main aspect about performance?
35. Excursus
36. Excursus Concurrency Doing more than one thing as the same time
37. Concurrency Concurrency Not just threading (parallelism) Q: Why did the multithreaded chicken cross the road? A: to To other side. get the — Jason Whittington
38. Concurrency Concurrency Threading is an issue - Simultaneous shared data access is hard. - Thread scheduling is non-deterministic - “Race conditions”
39. Concurrency Concurrency So what is concurrency? Concurrency is not (only) parallelism
40. Concurrency Concurrency vs Parallelism “Concurrent multithreading systems give the appearance of several tasks executing at once, but these tasks are actually split up into chunks that share the processor with chunks from other tasks. In parallel systems, two tasks are actually performed simultaneously. Parallelism requires a multi-CPU system.” —Timing Java Threads by Allan Holub
41. Concurrency Concurrency vs Parallelism So what is parallelism? “Programming as the simultaneous execution of (possibly related) computations.” — Rob Pike
42. Concurrency Concurrency vs Parallelism So what is concurrency? “Programming as the composition of independently executing processes.” — Rob Pike
43. Concurrency —Timing Java Threads by Allan Holub
44. Concurrency Concurrency vs Parallelism Composition of independent units is an issue “A property of systems in which several computations are executing simultaneously, and potentially interacting with each other.” — wikipedia.org
45. Concurrency Concurrency vs Parallelism So what is concurrency? Communication is key for coordination
46. Concurrency Why use go for concurrency? Python can concurrency java can concurrency but go is designed for concurrency
47. Concurrency Lets have an illustration
48. Concurrency Single thread Input CPU Tasks Output
49. Concurrency Single thread Input CPU Tasks Output CPU
50. Concurrency Multi thread Input CPU Tasks Output CPU Tasks
51. Concurrency Concurrency? Input CPU Tasks Output Input CPU Tasks Output
52. Concurrency Another model Input CPU Task 2 Output CPU Task 1 CPU Task 3
53. Concurrency Parallelise Input CPU Task 2 Output CPU Task 1 CPU Task 3 Input CPU Task 2 Output CPU Task 1 CPU Task 3
54. Concurrency Another model Input Temp store Output CPU Task 1 CPU Task 1
55. Concurrency More throughput Input Temp store Output CPU Task 1 CPU Task 1 Input Temp store Output CPU Task 1 CPU Task 1
56. Concurrency Combine models Input Temp store Output CPU Task 2 CPU Task 1 CPU Task 3 CPU Task 2 CPU Task 1 CPU Task 3
57. Concurrency Parallelise Input Temp store Output CPU Task 2 CPU Task 1 CPU Task 3 CPU Task 2 CPU Task 1 CPU Task 3 Input Temp store Output CPU Task 2 CPU Task 1 CPU Task 3 CPU Task 2 CPU Task 1 CPU Task 3
58. Concurrency Conclusion Many ways to split Split first, parallelise after Concurrent design
59. Concurrency How it this done in go? goRoutines Channels Selects
60. Concurrency GoRoutines A bit like threads but much cheaper Multiplexed across OS level threads
61. Concurrency GoRoutines A bit like threads but much cheaper Multiplexed across OS level threads
62. Concurrency Channels Means for synchronisation and information exchange
63. Concurrency Unbuffered channel
64. Concurrency Buffered channel
65. Concurrency Select Organise multiple channel operations
66. Concurrency Select
67. Concurrency What happens if I don't use channels?
68. Concurrency
69. Concurrency Conclusion Easy! Powerful!
70. thanks