[erlang-questions] Book: "Robust Communications Software: Extreme Availability, Reliability and Scalability for Carrier-Grade Systems"

Ulf Wiger ulf@REDACTED
Wed Dec 10 08:58:24 CET 2008


I haven't read it.

There's one customer review. Here's an extract:

"It points out that many aspects of a modern computer
system (pre-emptive multi-tasking, virtual memory, many
short-lived processes/threads to handle task execution and
dynamic garbage collection) are actually detrimental to the
design of a carrier-grade system. "

"[the developer team] shouldn't be put off by the C++ code
in the early chapters."

You can read parts of the book on-line via books.google.com,
and from a quick perusal, I'd say that it's a pretty good book
if you want an introduction into how to best write a carrier-class
system in C++. From what he writes, you can extrapolate that
Erlang is "dead wrong" for carrier-class systems(*). But then one
needs to remember that his frame of reference is /mainstream/
programming technology. If you have the time, it might be useful
to read the book, then read Joe's book, and meditate over the
differences in approach.

(*) This would be the superficial conclusion based on the fact that
he dismisses dynamic processes (because POSIX threads are un-
suitable for such programming), preemptive scheduling (because
it forces you to use semaphores everywhere), and dynamic
garbage collection (because it's very difficult to write a dynamic
garbage collector yourself that doesn't cause long pauses).

If your starting point is that there is no realistic alternative to
C++ for real industrial work, I'd say this kind of book is a must.

BR,
Ulf W

2008/12/10 Chris Newcombe <chris.newcombe@REDACTED>:
> Has anyone (particularly AXD301/ENGINE/OTP folks) read the following book?
>
>  "Robust Communications Software: Extreme Availability, Reliability
> and Scalability for Carrier-Grade Systems"
>   by Greg Utas
>
>   http://www.amazon.com/Robust-Communications-Software-Availability-Carrier-Grade/dp/0470854340
>
> Is it any good?
>
> thanks,
>
> Chris
>
> Extract from product summary:
>
> Carrier-grade software must satisfy the stringent quality requirements
> of network operators whose systems provide mission-critical
> communications services. This book describes proven carrier-grade
> software techniques used in flagship products designed by industry
> leaders such as Lucent, Nortel, and Ericsson.
>
> In the age of 24/7, software robustness is a competitive advantage.
> This authoritative guide for software engineers, managers, and testers
> of products that face carrier-grade requirements helps you to develop
> state-of-the-art software that will give you an edge in today's
> marketplace.
>
> Robust Communications Software: Extreme Availability, Reliability and
> Scalability for Carrier-Grade Systems
>
>    * offers advice on choosing the right technologies for building
> reliable software
>    * incorporates real-world examples and design rationales when
> describing how to construct robust, embedded software for
> communications systems
>    * presents a comprehensive set of carrier-grade design patterns
> that help you to meet extreme availability, reliability, scalability,
> and capacity requirements
>    * gives advice on how to protect against and recover from software faults
>    * discusses system installation, operability, maintenance, and
> on-site debugging
>
> Greg Utas has over 20 years of development experience in carrier-grade
> systems, including Chief Software Architect roles at Nortel Networks
> (GSM core networks) and Sonim Technologies (wireless push-to-talk
> services). He is currently a consultant specializing in the design of
> carrier-grade software.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>



More information about the erlang-questions mailing list