|
|
|
|
|
|
by Scarbutt
1648 days ago
|
|
|
4. Concurrency model that lets you spin up things in the background and keep processing in memory before you go into databases, worker queues, and whatnot. If you want to cache something slow, just put it in a map behind an RWMutex, and your single-process Go binary will scale way past any prototype stage. This the big one IMO when comparing to nodejs but a showstopper for some apps in ditching nodejs for Go is needing a nodejs process for SSR. |
|
|