Databases Reference
In-Depth Information
to really benefit from horizontal scale-out, your team is going to have to make some
paradigm shifts. Second, you should start to see that systems that are designed with
both concurrency and high availability in mind tend to be easier to scale.
This doesn't mean you need to write all your business applications in Erlang func-
tions. Some companies are doing this, but they tend to be people writing the NoSQL
databases and high-availability messaging systems, not true business applications.
Algorithms such as MapReduce and languages such as
HIVE
and
PIG
share some of
the same low-level concepts that you see in functional languages. You should be able
to use these languages and still get many of the benefits of horizontal scalability and
high availability that functional languages offer.
In our next chapter, we'll leave the abstract world of cognitive styles and the theo-
ries of computational energy minimization and move on to a concrete subject: secu-
rity. You'll see how NoSQL systems can keep your data from being viewed or modified
by unauthorized users.
10.8
Further reading
“Deadlock.” Wikipedia.
http://mng.bz/64J7
.
“Declarative programming.” Wikipedia.
http://mng.bz/kCe3
.
“Functional programming.” Wikipedia.
http://mng.bz/T586
.
“Idempotence.” Wikipedia.
http://mng.bz/eN5G
.
“Lambda calculus and programming languages.” Wikipedia.
http://mng.bz/15BH
.
MSDN
. “Functional Programming vs. Imperative Programming.”
http://mng.bz/8VtY
.
“Multi-paradigm programming language.” Wikipedia.
http://mng.bz/3HH2
.
Piccolboni, Antonio. “Looking for a map reduce language.” Piccolblog. April 2011.
http://mng.bz/q7wD
.
“Referential transparency (computer science).” Wikipedia.
http://mng.bz/85rr
.
“Semaphore (programming).” Wikipedia.
http://mng.bz/5IEx
.
