Notes on "What is Hadoop? Other big data terms like MapReduce? Cloudera's CEO talks" video

• Map reduce - spread processing of data over many computers so data can be processed in parallel with cheaper hardware.  No transactions or schema.  Aimed more at analysis (Reads) rather than full CRUD?
• Relational databases not good for unstructured free text  
• Hadoop - open source, consists of (1) distributed file system to spread out data (HDFS), (2) way to push code down to do data analysis on the data 
• Scalable because can just drop in more servers 
• Memcached - in memory cache of relational database, push through writes "incrementally"? 
• NoSQL - distributed hash tables
• Sharding (not discussed in video) - taking rows of a relational table and distributing across computers

Notes on early TSS.NET Unit Testing article

• Article
• "A test fixture is a class that contains a series of test methods ... This grouping is important for two main reasons: one, it creates a subset of tests that can be run as a group, separate from other groups of tests, and two, it provides a level of granularity for controlling the lifecycle and context of a test."
• For database code, article suggests using stored procedures to initialize database for a unit test and calling these stored procedures in SetUp and TearDown.  Also, more specific stored procedures to create additional data for specific tests.  More ideas:  Get Test Infected with NUnit: Unit Test Your .NET Data Access Layer 
• a mock object will have the same interface as the "real" object.  The implementation of the mock object should track usage, allowing you to determine if the right calls were made (by the tested code), and expose any methods/properties that test code might use to evaluate results.  Rather than implement yourself, can use a dynamic mock object library such as NMock
• Nester helps verify code coverage by unit testing:  "involves modification of programs to see if existing tests can distinguish the original program from the modified program" (mutation testing)
• So that test code doesn't force breaking encapsulation of the tested code, have tests reside in same assembly and namespace as code being tested.  Then non-public methods/properties that need to be accessed by test code can be marked with internal modifier

Jersey, JAX-RS notes on Jersey 1.3 User Guide

• Jersey 1.3 User Guide
• a more detailed document than the "RESTful Web Services Developer's Guide", especially regarding JSON support and the Jersey client API 
• example of "Builder" pattern utilized by Jersey client API, rather than the JavaBean get/set pattern:
  
  

  8   JAXBBean bean = r.
  9     type(MediaType.APPLICATION_FORM_URLENCODED_TYPE)
  10    .accept(MediaType.APPLICATION_JSON_TYPE)
  11    .post(JAXBBean.class, f);
  

Jersey, JAX-RS notes for RESTful Web Services Developer's Guide

• RESTful Web Services Developer's Guide
• can embed variables in the URIs. URI path templates are URIs with variables embedded within the URI syntax
• "A fundamental part of REST is that the next set of valid operations is encoded in the response from the last. This means that as long as you only use actions from the last operation you will always perform a valid operation according to the application protocol." - does this feature exist in Jersey?
• "If a character in the value of a variable would conflict with the reserved characters of a URI, the conflicting character should be substituted with percent encoding." - use case?
• If the application needs to supply additional metadata, such as HTTP headers or a different status code, a method can return a Response that wraps the entity, and which can be built using Response.ResponseBuilder.
• By default, a resource class can respond to and produce all MIME media types of representations specified in the HTTP request and response headers