DenkzeitWiki

Suchen:

Aktuelle Änderungen Printable View Änderungen Bearbeiten

BehaviorDrivenDesign > SmartDataAndDumbCode > ProgrammingLanguages > ProgrammierSprachen > JavaEnterpriseEdition > DataDrivenProgramming > TestDrivenDevelopment > ClojureReferenceTypes > VersionControlSystems > VersionControl > FunctionalProgramming > SomeOfMyPythonScripts > CommonLanguageRuntime > GlobalInterpreterLock > SoftwareCraftsmanship > PrematureOptimization > ConcurrentProgrammingClear Trail
Main /

Concurrent Programming

Concurrency
MultiThreading
MulticoreProgramming
SoftwareTransactionalMemory

Scalability

Closures

ActorModel

Erlang
Clojure

Threads are not the answer. Threads are the question. No is the answer. Why? Scalable != threading. Scalable == clustered / peer to peer / grid.[1]







We need to be headed primarily toward shared *nothing*. Sharing at the level prescribed in this paper, whether with locks or transactions, is simply uncalled for 99% of the time. Sequential processes with shared-nothing message passing should be the direction.


Lock-based programming, our status quo, is difficult for experts to get right. Worse, it is also fundamentally flawed for building large programs.
...
Lock-free programming is difficult for gurus to get right.









Concurrency Vs. Parallelism








Languages

Oz


Python Python



Java


Erlang


Introductions




Message Passing


MultiThreading with Python






Distributed Concurrency


The ErlangVM enables distributed concurrency, Closure on the JVM is optimizing for local concurrency.


Edit - BackLinks - Tags - Page Hist - Print - Changes - Home - Orphans - Help

Zuletzt geändert am 06.11.2010 20:58 Uhr und seit 7. April 2005 5600 aufgerufen.