3

Besides the benefits of this model over the shared-memory model, I'm just trying to understand where to apply it for higher levels use-cases.

keiter
  • 3,534
  • 28
  • 38
rbajales
  • 1,010
  • 1
  • 9
  • 14

2 Answers2

1

As to Scala, Actors model fits most of the multi-threaded cases one can think about:

  • Swing GUI application
  • Web Applications (see Lift framework)
  • Application Server in multicore environment:
    • Batch processing of requests/data
    • Background tracking tasks
    • Notifications & Scheduled tasks

Actors model makes design much clearer and greatly simplifies interprocess communication.

Nikita Skvortsov
  • 4,768
  • 24
  • 37
0
  • OTP Framework : Provides really good framework for network based applications.

  • Helps in making fault tolerant applications . (process restart using Supervisor's in OTP).

  • Both Synchronous and Asynchronous modes of communication can be done using gen_server.

  • Event based callbacks can be used using gen_event.

  • State machine can be programmed easily using gen_fsm (In case you need to follow some states in your application).

  • A process crash does not bring the whole application down. Only that particular process crashes.

  • Functional programming language.

  • A lot easier to program at binary level.

  • Garbage collection.

  • Native compilation option.

  • Fair amount of good useful modules are available.

  • Able to make good solid concurrent applications easily.

And lots more.... I really enjoyed working on some applications in erlang , making those in c/c++ would have been very difficult.

Pablo Fernandez
  • 103,170
  • 56
  • 192
  • 232
Arunmu
  • 6,837
  • 1
  • 24
  • 46