Text CB3A1AAA
Like humans, computers can team up with their peers to achieve results that none of them could obtain alone; unlike humans, they can do many activities at once, and do all of them well. In spite of that, passé debates on this issue have implicitly assumed that computation is mostly sequential — proceeds along a single thread of control. Software developers should now realize that this assumption no longer holds, as we move to concurrent (also known as parallel) computation.
Concurrency is not a new subject, but for a long time interest in it remained confined to four application areas: operating systems, networking, implementation of database management systems, and high-speed scientific software. Although strategic and prestigious, these tasks involve only a small subset of the software development community. Things have changed. Concurrency is quickly becoming a required component of just about every type of application, including some that had traditionally been thought of as fundamentally sequential in nature.
This advancement gives particular urgency to the study and review of various forms of concurrency; the evolution of Computer Science requires software developers to make concurrency part of their mindset. And it is not simply the traditional concepts of multiprocessing and multiprogramming, the past few years have introduced state-of-the-art technologies, such as remote execution through the Net.
Bertrand Meyer. Concurrency, distribution, client-server and the Internet.
In: Object-oriented software construction. 2th ed. New Jersey: Prentice Hall PTR, 2009, p. 951-3 (adapted).
Judge the following item according to the text CB3A1AAA.
Software construction professionals must be acquainted with concurrency quickly.
