Learning from past projects, Jeff Gothelf helped synthesize Lean UX into a growing practice within software firms of all sizes, where teams focus on project outcomes and not output. When teams of varying competencies are brought together from the beginning of a project and given ownership, they are able to take responsibility for delivering a great client experience.
Enterprise cloud specialist Brian McCallion talks about what's really holding back enterprises from adopting the cloud, how they should address their legacy applications, ways to avoid introducing complexity in distributed environments, the value of Amazon Redshift, and how technologists should broaden their knowledge and avoid specialization.
Jeff Patton helps teams build better products by helping them understand their users in a more thoughtful manner. By using the principles of comaking, teams begin to take more responsibility for their projects and their outcomes, thereby creating a more streamlined process of meeting their users' needs and having fun while doing it.
Cloud leader George Reese answers questions across a wide range of topics. He shares his thoughts on pitfalls of enterprise cloud strategies, overrated technologies, whether IaaS standards matter yet, the relevance of private clouds, and the need for common sense when designing a API.
Sadek talks about the origins of Playframework, motivations behind 2.0 rewrite and Scala integration. He explains how important is it to have appropriate architecture and programming model while dealing with Realtime. He then reveals some features of the newly released 2.1 version.
George Dinwiddie sits down with InfoQ at Agile 2012 to discuss the Three Amigos (Business, Programmers, and Testers) and how they need to interact and use examples in order to get a shared vision.
In this InfoQ interview, Michael Nygard explores some of the available loopholes in the CAP theorem helping architects to engineer distributed systems that meet their needs. He also discusses new patterns he’s observed since his book, Realease IT and shares his thoughts on continuous delivery, DevOps and ALM.
Emil Eifrem looks back at the history of Neo4j, an open-source, NoSQL graph database supported by Neo Technology. He describes some real world applications of graphs, domain modelling with graphs, and compares the performance of graph and relational databases. He also examines how Neo4j differs from other NoSQL and graph databases in the market and describes various Neo4j licensing options.
Big Data means more than just the size of a dataset. Pavlo Baron explains different ways of applying Big Data concepts in various situations: from analytics, to delivering content, to medical applications. His larger vision for Big Data ranges from specialized Data Scientists, to learning Decision Support Systems, to helping mankind itself.
Ian Robinson discusses Neo4J's design choices for data storage and retrieval, CRUD operations, transactions, graph traversal and searches and HA deployment strategies. He also shares his thoughts on hypermedia controls and the concept of consumer driven contracts for continuous evolution of services.
In this interview, Michael Hunger talks about the evolution of persistence technologies over the last decade, the emergence of NoSQL databases, and looks at where graph databases fit in. He describes the goals behind the Spring Data Neo4j project, it's latest developments, and examines Cypher, a humane and declarative query language for graphs.
In this interview we talk with Adrian Cockcroft, the architect for Netflix’s cloud systems team. We discuss how Netflix combines 300 loosely coupled services across 10,000 machines. An interesting revelation is that they fully embrace continuous delivery and each team is allowed to deploy new versions of their service whenever they want.