Stuart Dabbs Halloway, after reviewing Clojure’s syntax comparing it with Java, explains how Clojure-Java interoperability works. He then talks about the need for simplicity in languages, attempting to prove that Clojure is a simpler language, and consequently better, than Java.
Eishay Smith discusses the advantages of using continuous deployment (CD) at a rapid pace, dozens of times a day, the process and the tools needed to attain CD, and practices to ensure code quality.
Lloyd Taylor talks about different types of organizational culture, how to understand the culture one is in, what to do to be successful in the respective organization, and how to prepare for change.
Guilherme Silveira considers that RESTful web services need to make use of hypermedia in order to be prepared for web integration. He shows how links can be used to create more decoupled services.
Ryan Dahl demonstrates how to use Node.js’ asynchronous IO model to write simple HTTP/TCP/DNS servers that scale up serving thousands of connections while using a very low memory footprint and few CPU cycles.
Ron Bodkin presents the architecture used by Quantcast to process 100s of TB of data daily using Hadoop on dedicated systems, the applications, the type of data processed, and the infrastructure used.
Adrian Cockcroft discusses the advantages of running Netflix services in Amazon’s cloud, comparing the old data center solution against the new cloud architecture implemented to offer faster, more scalable, more available, and more productive services across the enterprise.
Martin Thompson and Michael Barker talk about building a HPC financial system handling over 100K tps at less than 1ms latency by having a new approach to infrastructure and software. Some of the tips include: understand the platform, model the domain, create a clear separation of concerns, choose data structures wisely, and run business logic on a single thread.
Stefan Tilkov makes a case for using REST in an enterprise SOA solution showing how to implement tricky features like encapsulation, transactions, stateful communication, reliable messaging, notifications, and security. He also offers advice on how to convince the management to use REST and how to implement it at the enterprise level, including mixing it with WS* when mandatory.
Marius Eriksen considers that scalability problems appear when leaky abstractions are used, exemplifying with RDBMS, GC, and threads, presenting abstractions that help dealing with scalability issues: map-reduce, shared-nothing web applications, big table, all providing narrow access to explicit resources.
Ashish Kumar presents how Google manages to keep the source code of all its projects, over 2000, in a single code trunk containing hundreds of millions of code lines, with more than 5,000 developers accessing the same repository.
Blake Dournaee presents Intel’s Service Gateway, a security control point meant to secure on-premise and in the cloud .NET or Java platforms from various security threats like spoofing, tampering, repudiation, information disclosure, DoS, elevation of privilege, all of that in the context of today’s REST or SOAP web services.