Rachel Reese on the challenges and benefits of using microservices at Jet. In particular how F# made it easier to refactor and maintain hundreds of microservices. The hard bit is the infrastructure.
Peter Alvaro discusses some of the reasons that distributed programming is hard, Lineage-driven Fault Injection, static analysis to check deterministic behaviour, CRDTs, and much more.
Gil Tene speaks to Alex Blewitt at QCon London 2016 on the upcoming support for hardware transactional memory in server-class Intel chips, and what it will mean for the JVM. Tene discusses what kinds of applications will benefit from speculative lock elision and increasing concurrency in the near future on multi-core server platforms.
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.
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.
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.
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.
Microservices have been a trending topic for some time now and while we talked a lot about concepts in the past there are more and more real-life experiences to draw on now. In this interview, Michael Bryzek, co-founder and former CTO of Gilt, shares some of his experience working with microservices including how we should design our architectures and APIs to avoid ending up in a dependency hell.
Everybody has been talking about microservices for at least two years now and there are a lot of companies trying to migrate to that promising new architecture. We spoke to Sylvia Isler - VP of architecture at VMTurbo - about the reasons to migrate to microservices and how to turn an existing monolith into a distributed, resilient services landscape.
Mary and Tom Poppendieck talk to Charles Humble about continuous delivery, architects, management and other senior roles in IT, and diversity in the industry.
Randy Shoup talks about designing and building microservices based on his experience of working at large companies, such as Google and eBay. Topics covered include the real impact of Conway's law, how to decide when to move to a microservice-based architecture, organizing team structure around microservices, and where to focus on the standardization of technology and process.