Which is safer for concurrent data access? Channels or Maps?

1.	Which is safer for concurrent data access? Channels or Maps?
Answer» Channels are safe for concurrent ACCESS because they have blocking/locking mechanisms that do not LET goroutines share MEMORY in the presence of multiple threads. Maps are unsafe because they do not have locking mechanisms. While using maps, we have to use explicit locking mechanisms like mutex for safely SENDING data through goroutines.

Answer»

Channels are safe for concurrent ACCESS because they have blocking/locking mechanisms that do not LET goroutines share MEMORY in the presence of multiple threads.

Maps are unsafe because they do not have locking mechanisms. While using maps, we have to use explicit locking mechanisms like mutex for safely SENDING data through goroutines.

Discussion

No Comment Found

Related InterviewSolutions

What do you understand by byte and rune data types? How are they represented?
What do you understand by variadic functions in Go?
What do you understand by Shadowing in Go?
How can you sort a slice of custom structs with the help of an example?
Which is safer for concurrent data access? Channels or Maps?
In Go, are there any good error handling practices?
How is GoPATH different from GoROOT variables in Go?
How can we copy a slice and a map in Go?
What are the uses of an empty struct?
Is the usage of Global Variables in programs implementing goroutines recommended?

Which is safer for concurrent data access? Channels or Maps?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment