InfoQ Homepage Presentations
-
Pragmatic SOA Beyond Buzzwords and Flamewars
Stefan Tilkov discusses SOA basic concepts by making a number of claims, such as “An ESB should not be at the core of your SOA”, followed by explanations and related recommendations.
-
Does the Cloud Need DevOps? Does DevOps Need the Cloud?
Examining the role that cloud technologies can play in solving DevOps problems and the role that DevOps solutions can play in getting the most out of cloud technologies.
-
Learning from Five Years as a Skype Architect
Andres Kutt shares lessons learned at Skype: rules of thumb don’t always apply, functionality is important, simple solutions, buzzwords are dangerous, and communication is important.
-
Demystifying Monads
Josh Graham explains what monads are, how and why they are used, including several concrete examples of monads like Identity, Maybe, List, and Continuation.
-
Feature Bits: Enabling Flow Within and Across Teams
Erik Sowa and Rob Loh present the Feature Bits technique used by Lyris, detailing the business context, the solution design, the data model, and coding patterns, plus lessons learned using it.
-
Deploying Java Applications on Amazon EC2
Chris Richardson on deploying Apache/Tomcat/MySQL apps on Amazon EC2, what it takes to deploy all servers, making a case for PaaS which does not require an administration effort.
-
Changing Culture to Enable DevOps
Changing tools is easy when compared to changing people and processes. How can we cultivate an organization’s culture to identify and solve DevOps problems?
-
Introduction to Bespin - Mozilla's Web Based Code Editor
Joe Walker explains Bespin, Mozilla’s open source web-based code editor, its architecture and chosen implementation solution, detailing some of its features like collaboration and version control.
-
The Lean Influencer’s Mantra
Siraj Sirajuddin talks about the Change Agent’s role in introducing Lean and Kanban in large organizations, the Lean philosophy, the forces and dynamicas related to Lean and Kanban adoption.
-
Death by Accidental Complexity
Ulf Wiger shows how concurrency can lead to accidental complexity if it is badly implemented in code, becoming a project’s point of failure. Wiger also advises on how concurrency should be addressed.
-
Your Mileage May Vary
Experiences and lessons learned facing DevOps problems in the IT trenches (even if they weren’t calling it DevOps!). The good, the bad, the surprises, and ideas for the future.
-
Sustainable Design for Agile Teams
Eric Evans advocates on gradual blending of modeling and design into iterative development in an attempt to create a solution that expresses the domain and is flexible enough to support changes.