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.
Camille Fournier explains how Rent the Runway uses software and data science to handle a massive shipping and warehouse operation, modelling inventory life cycles, optimising shipping and much more.
Matthew Skelton talks about the challenges to DevOps and Continuous Delivery adoption, what's the impact of microservices in this space, how to leverage ITIL, and DevOps team topologies.
Caitie McCaffrey talks about scaling game backend services for Halo 4 and others, stress & performance testing, the Orleans actor framework, and the future of distributed programming.
Rebecca Parsons, Thoughtworks CTO, on microservices: prerequisites, challenges and benefits. Also insights on designing services for scalability, handling failure and eventual consistency.
Mike Long explains how to build software for the long term, software maintenance, how some software survives. Also a thought experiment - how would you build software that lasts for 10,000 years?
Yan Cui talks about the advantages of using F# to build DSLs and using the actor model. Also: why and how to use graph databases to model (game) economies.
Natalia Chechina explains the challenges of scaling distributed Erlang beyond a certain number of systems and how SD Erlang helps to overcome those problems.
Barbara Fusinska explains the challenges of building offline mobile applications: synchronisation, API design, data modeling, and much more.