Explore >> Select a destination
|
You are here 
|
www.thepolyglotdeveloper.com | ||
| | | | |
bartlomiejmika.com
|
|
| | | | | Learn how to protect API endpoints with access and refresh tokens using the third-party jwt-go library. | |
| | | | |
electric-sql.com
|
|
| | | | | Web development has been progressing through an evolution of state transfer. Hybrid local-first architecture is the natural endgame for this progression. | |
| | | | |
www.prisma.io
|
|
| | | | | GraphQL Nexus is a code-first, type-safe GraphQL schema construction library for JavaScript/TypeScript. Learn how it can be connected to a database using the Prisma client & the new nexus-prisma plugin. | |
| | | | |
konradreiche.com
|
|
| | | Starting a goroutine is as easy as adding the go keyword in front of a method, but managing the lifecycle of a goroutine is not. If you only need to start a few goroutines and wait for their completion, you are off the hook thanks to sync.WaitGroup. However, what if a goroutine has to run for a specific duration or repeatatly in a loop until the initiating code terminates? Does it matter? After all, if the main goroutine terminates, any other goroutine will also stop. It does matter, because depending on what the goroutines are doing, it might leave your system in an inconsistent or invalid state. Channels are a commonly used to signal to a goroutine that it can shut down, but I often see the use of a signaling channel, for example chan bool or chan struct{}... | ||
