InfoQ Homepage Architecture Content on InfoQ
-
Ian Robinson discusses REST, WS-* and Implementing an SOA
In this interview from QCon San Francisco 2008, Ian Robinson discusses REST vs. WS-*, REST contracts, WADL, how to approach company-wide SOA initiatives, how an SOA changes a company, SOA and Agile, tool support for REST, reuse and foreseeing client needs, versioning and the future of REST-based services in enterprise SOA development.
-
Rod Johnson About Spring Framework 3.0 & Others
In this interview made by Srini Penchikala, with the participation of Ryan Slobojan, Rod Johnson answered many questions about Spring Framework 3.0 and other applications developed under SpringSource’s umbrella - Tool Suite, Integration, Web Flow, Batch – talking about their current status and existing plans for the future.
-
Yehuda Katz explains Merb
In this interview from RubyFringe, Yehuda Katz talks about Merb, its design principles, and how it differs from Rails. Yehuda also mentions Yard, an RDoc replacement.
-
Scott Ambler On Agile’s Present and Future
In this interview, InfoQ’s Chief Editor, Floyd Marinescu, interviewed Scott Ambler, Practice Lead for Agile Development at IBM, on the current status of the Agile community and practices having a look at the perspective of the Agile’s future.
-
Damien Katz Relaxing on CouchDB
In this interview, Damien Katz talks about CouchDB, a distributed, fault tolerant, document oriented database developed by Apache Incubator. CouchDB is written in Erlang, and the database is accessed through an HTTP/JSON API. The database view engine is run on JavaScript, but other languages have been used like Ruby and Python.
-
Dan Farino On MySpace’s Architecture
In this interview taken by InfoQ’s Ryan Slobojan, Dan Farino, Chief Systems Architect at MySpace, talks about the system architecture and the challenges faced when building a very large online community. Because MySpace is built almost entirely on the .NET Framework, Dan explains how a .NET product scales on hundreds of servers.
-
Joe Armstrong About Erlang
In this interview filmed during QCon London 2008, Joe Armstrong, designer of Erlang, speaks on various aspects of the Erlang language, presenting its roots, how it compares with other languages and why it has become popular these days due to its native ability to scale on multi core systems.
-
Pressure and Performance – The CTO's Dilemma
In this interview made by Deborah Hartmann during Agile 2008, Diana Larsen and Jim Shore talk about patterns observed in CTOs' activity. CTOs emerge as real people caring for other people in their organization, and are put under a lot of pressure and constraints.
-
Steven "Doc" List About Open Spaces
In this interview made by InfoQ's Greg Young, Steven "Doc" List talks about Open Space conferences, a way of running meetings of groups of various sizes by facilitating self organizing the sessions.
-
Alexandru Popescu Discusses the InfoQ.com Site Architecture
In this interview from QCon London 2008, InfoQ Chief Architect Alexandru Popescu discusses the architecture of InfoQ, integrating WebWork and DWR, Hibernate and JCR, Hibernate scalability, MySQL replication, the new InfoQ video streaming system, the video encoding process, site search, and future plans for InfoQ.
-
Simon Peyton Jones on Programming Languages and Research Work
In this QCon London 2008 interview, computer scientist and researcher Simon Peyton Jones discusses properties of functional programming languages, and particularly Haskell, that have inspired some features in mainstream languages. He gives his opinion on the issues of syntax and language complexity and talks about some research work on subjects such as Data parallelism and transactional memory.
-
Erich Gamma Discusses Jazz, Eclipse, JUnit and Design Patterns
In this interview from QCon London 2008, Erich Gamma discusses the Jazz project, why Eclipse has been successful, the strict Eclipse release schedule, JUnit, Design Patterns, how to identify a design pattern, design patterns and the 'Don't Repeat Yourself' principle, the design pattern community, and whether dependency injection is a design pattern.
