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.
Martin Kleppmann explains how logs are used to implement systems (DBs, replication, consensus systems, etc), integrating DBs and log-based systems, the relevance of CAP and CRDTs, and much more.
Sadek Drobi explains ways to simplify software architectures by reframing the problem and requirements. Also: Scala, Prismic.io, and much more.
Architecture design is defining the basic structure of our software for now and for the future. But how can this work, given that we are living in an agile world accepting the fact that we only have limited knowledge of our final system? InfoQ was talking with Colin Garlick about architecture design and responsibilities during software development.
Neha Narula talks about the latest research and concepts in distributed programming and databases, reducing the overhead of transactions, are multicore systems like distributed systems, and much more.
Mitchell Hashimoto explains how Vagrant, Consul, Terraform and Atlas help developers and ops to set up complex systems and keep them running. Also: Go as a language for tools.
Camille Fournier explains consensus systems ZooKeeper, etcd, and Consul: how they work, what they do, how they differ from each other. Also: must-read papers in distributed programming.