Explore >> Select a destination
|
You are here 
|
damienradtke.com | ||
| | | | |
darrenparkinson.uk
|
|
| | | | | Using the Cisco Webex Meetings XML APIs | |
| | | | |
kubamartin.com
|
|
| | | | | Practical Golang: Getting started with NATS and related patterns Introduction Microservices... the never disappearing buzzword of our times. They promise a lot, but can be slow or complicated if not implemented correctly. One of the main challenges when developing and using a microservice-based architecture is getting the communication right. Many will ask, why not REST? As I did at some point. Many will actually use it. But the truth is that it leads to tighter coupling, and is synchronous. | |
| | | | |
hjr265.me
|
|
| | | | | Concurrency is one of the central features of Go. And, to build concurrent programs in Go, you need goroutines. A goroutine is like a thread, but lighter. Much lighter. And, like any other built-in feature of Go, using it is dead simple: 1 2 3 4 5 6 7 package main func main() { go func() { println("Hello World") // Print "Hello World" from a different goroutine. }() } Wait. That didn't print anything. | |
| | | | |
usher.dev
|
|
| | | |||
