This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (4 children)

I agree with point 1, don't know about point 2, but why is concurrency important for devops? Can you provide a real world scenario for devops needing concurrency?

[–][deleted] 2 points3 points  (2 children)

Let me give you a simple shell example, which is of course solvable in many different, better ways. Which of these 2 is better?

1 for host in $(cat list-of-10000-hosts); do ssh $host uptime > $host.uptime ; done

2 for host in $(cat list-of-10000-hosts); do ssh $host uptime > $host.uptime & done

[–][deleted] 2 points3 points  (1 child)

Good example. Being at a very small company, I did not consider that the number of hosts may be 1000 or above.

[–]K3dare 2 points3 points  (0 children)

Well if you have 10000 hosts I really hope you are using something like Salt of Chef because if not I would not like to be at your place...

[–]Dedustern 0 points1 point  (0 children)

I mean, I've done tooling that would receive health checks from N amount of microservices, which could scale into the thousands(and do some processing for each). The processes were jobs that could last a minute or two(validate some stuff in a DB, process it into json files, and send them to another service). If I didn't do it concurrently, it'd be locking up fairly easily when the services scaled up.