Adrian Colyer explains the motivation behind publishing the "Morning Paper" (a blog discussing Computer Science research papers) and mentions some of his favourite papers of the past year.
In this interview, John Sheehan expounds on what constitutes a high quality API. The first half focuses on developer experience which will help API consumers distinguish between top tier API providers and the rest. The second half provides pointers for API providers aiming to improve various aspects of API quality, specifically performance across the API lifecycle.
Josh Long talks about the philosophy behind Spring Boot and Spring Cloud. He also discusses some of the common distributed computing problems Pivotal are trying to solve - externalised configuration, service discovery, client-side load balancing, distributed tracing and so on, and talks about some major clients including Netflix, Baidu and Alibaba.
Gil Tene explains latency and how it relates to service and response times, measuring latency, common misconceptions about latency, what to do when a system's latency can't meet SLAs, and much more.
Performance engineer Monica Beckwith covers tuning java garbage collection, including: defining customer requirements; methodology; baselining and measurement; strengths and weaknesses of the different collectors; heap usage; causes of GC pauses; the distribution of pauses; tuning pause characteristics; going off-heap to avoid collection; scaling GC on multi-core and high memory machines.
Bridget Kromhout explains Cloud Foundry, how to run or use it, the tools Cloud Foundry provides for automation, and much more.
The interview with Jon Moore begins with a discussion on the relevance of Hypermedia APIs in the context of micro-services as well as the impact of HTTP 2.0 on APIs in general.The second half of the interview focuses on event causality in distributed systems and Moore's research on the application of population protocols for better clock synchronization.
Adam Wick talks about software security, research into formal methods and randomisation as well as documentation and types to help write secure software, HalVM and other Unikernels, DRM.
Modern software systems are complex and chaotic. Requirements, employee counts, and production environments change quickly. Yet the software produced under these circumstances must be understandable as well as useful. Matt Ranney, an architect at Uber, argues that to understand these complex systems you must embrace chaos, rather than run from it. You must also accept limits to our understanding.
Rick Hudson talks to Charles Humble about the evolution of Go’s garbage collector, comparing 1.5 to the forthcoming 1.6 release, and also touching on plans for 1.7.
Bryan Cantrill explains Triton (a way to run secure Linux containers on bare metal), the history of DTrace and ZFS and their (lack of) adoption on Linux, the relevance of OS R&D, Unikernels and more.
Chris Richardson explains the appeal of Scala, functional programming in Java and other languages, the basics of Event Sourcing, and his perspective on the state of the Java ecosystem.