Go & Concurrency

Go adalah bahasa pemograman yang mudah digunakan untuk membuat aplikasi yang simpel dan efisien.

Go sendiri merupakan bahasa pemograman yang dibuat oleh salah satu tim di Google dan berbagai kontributor dari dunia open source.

Go merupakan bahasa pemograman yang perlu dicompile, seperti C dan C++, menggunakan static typing, garbage collection, dan fitur unik yang didesain untuk konkurensi.

Pada slide ini akan menjelaskan dasar tentang konkurensi dan pengaplikasiannya menggunakan Go lang.

Transcript

1. GO & Concurrency HENDYANTO- KMKLABS
2. Hello! I am Hendyanto Vidio.com developer
3. About GO Go is an open source programming language that makes it easy to build simple, reliable, and efficient software. Go is an open source project developed by a team at Google and many contributors from the open source community. Go is a compiled programming language in the tradition of C and C++, with static typing, garbage collection, and unique language features enabling concurrent programming
4. Introducing.. Gophers
5. Sample Code main.go: package main func main() { println(“Hello!”) }
6. Run / Build Example Run: go run main.go Build & execute: go build && ./hello
7. Package Go projects are grouped by package, which consists of one folder with many .go files. All of them will be compiled into 1 executable.
8. Visibility func and type that has been defined with Capital letter is publicly visible Visible: func DoThis() { } Not Visible: func doThis() { }
9. Importing Packages package main Import “fmt” Func main() { fmt.Printf(“Hello world!”); }
10. Interesting Features - Variables can use utf-8 characters var test = “Super” var 你怎么样 = “Apa Kabar” - Support for multiple return values from function func someFunc() (int, int) { return 7, 10 }
11. Go Concurrency The juicy part
12. Why concurrency? Look around you. What do you see? Do you see a single-stepping world doing one thing at a time? Or do you see a complex world of interacting, independently behaving pieces? That's why. Sequential processing on its own does not model the world's behavior.
13. Concurrency is not parallelism Says everyone else talking about concurrency Concurrency is not parallelism, although it enables parallelism. Concurrency is about dealing with lots of things at once. Parallelism is about doing lots of things at once. Concurrency is about structure, parallelism is about execution.
14. Example Move a pile of obsolete language manuals to the incinerator. With only one gopher this will take too long.
15. More gophers! More gophers are not enough; they need more carts.
16. More gophers and more carts This will go faster, but there will be bottlenecks at the pile and incinerator. Also need to synchronize the gophers. A message (that is, a communication between the gophers) will do.
17. Double everything Remove the bottleneck; make them really independent. This will consume input twice as fast.
18. Another Design Three gophers in action, but with likely delays. Each gopher is an independently executing procedure, plus coordination (communication).
19. Finer-grained concurrency Add another gopher procedure to return the empty carts. Four gophers in action for better flow, each doing one simple task. If we arrange everything right (implausible but not impossible), that's four times faster than our original one-gopher design.
20. Another Design Here's another way to structure the problem as the concurrent composition of gopher procedures. Two gopher procedures, plus a staging pile.
21. Bring the staging pile to the multi-gopher concurrent model: Apply the last model
22. Now we have 16 gophers at work! Parallelize it!
23. What is a goroutine? It's an independently executing function, launched by a go statement. It has its own call stack, which grows and shrinks as required. It's very cheap. It's practical to have thousands, even hundreds of thousands of goroutines. It's not a thread. There might be only one thread in a program with thousands of goroutines. Goroutine
24. Channels Channels serve to synchronize execution of concurrently running functions and to provide a mechanism for their communication by passing a value of a specified type. It is about sending and receiving messages between goroutines.
25. There are many ways to break the processing down. That's concurrent design. Once we have the breakdown, parallelization can fall out and correctness is easy. Summary
26. Real World Analogy
27. The Problem Goal Serve bubur to a lines of 10 customers in the busy morning in front of Ratu Plaza. Tasks 1. Siapkan dan jejerkan kotak styrofoam 2. Masukkan bubur dari panci ke kotak 3. Tanyakan topping yang diinginkan dan taburkan diatas bubur 4. Bungkus, minta bayaran dan serahkan pada pembeli
28. Actors 1. Buburman
29. Delegation & Timing 1. Buburman → Deretkan kotak (1 detik) 2. Buburman → Masukkan bubur (2 detik) 3. Buburman → Topping (3 detik) 4. Buburman → Bayaran dan bungkus (1 detik)
30. Using Sequential Design 1. Buburman Satu → Deretkan kotak (1 detik) 2. Buburman Satu → Masukkan bubur (2 detik) 3. Buburman Satu → Topping (3 detik) 4. Buburman Satu → Bayaran dan bungkus (1 detik) 5. Kembali ke 1 1 Workers 7 detik / Customer Total 70 detik
31. Concurrent Design Actors 1. Buburman Satu 2. Buburman Dua 3. Buburman Tiga 4. Buburman Empat
32. Using Concurrent Design 1. Buburman Satu → Deretkan kotak (1 detik) 2. Buburman Dua → Masukkan bubur (2 detik) 3. Buburman Tiga → Topping (3 detik) 4. Buburman Empat → Bayaran dan bungkus (1 detik)
33. Concurrent Design - sec 0 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
34. Concurrent Design - sec 1 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
35. Concurrent Design - sec 2 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
36. Concurrent Design - sec 3 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
37. Concurrent Design - sec 4 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
38. Concurrent Design - sec 5 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
39. Concurrent Design - sec 6 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
40. Concurrent Design - sec 7 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
41. Concurrent Design - sec 8 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
42. Concurrent Design - sec 9 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
43. Concurrent Design - sec 10 B1 B2 B3 B4 1 2 3 4 5 6 7 8 9 10
44. And so on..
45. Using Concurrent Design 1. Buburman Satu → Deretkan kotak (1 detik) 2. Buburman Dua → Masukkan bubur (2 detik) 3. Buburman Tiga → Topping (3 detik) 4. Buburman Empat → Bayaran dan bungkus (1 detik) 4 Workers 7 detik / bubur Total 34 detik
46. Demo 1. Tukang bubur 2. Image Scraper
47. Q & A
48. Reference https://talks.golang.org/2012/concurrency.slide#1 https://golang.org/project/ http://talks.golang.org/2012/waza.slide#15 http://guzalexander.com/2013/12/06/golang-channels-tutorial.html GoJakarta (https://github.com/kenshaw/go-jakarta/) Codes Sample https://github.com/hendyanto/techtalk-kmklabs
49. Computers are good at following instructions, but not at reading your mind. Donald Knuth American computer scientist, mathematician, and professor emeritus at Stanford University
50. Thank you Any developer watching this, you should go and apply to KMKLABS they are cool!