Jim Hirschauer describes the application monitoring tool landscape, KPIs and metrics to consider when monitoring, and compares monitoring traditional vs. cloud-based applications. He talks about performance considerations when instrumenting code, how organizations can be 'Smarter' about their Big Data, and looks at what's new in AppDynamics 3.7.
Barbara Liskov keynoted at QCon London 2013 on the power of abstraction. Afterwards, InfoQ caught up with up with her to ask her about language design, modularity and distributed computation.
Through teamwork, an agile team can ensure the quality of its project's architecture, code hygiene, and other non-functional requirements by explicitly creating tasks for those concepts in each sprint. Alexander von Zitzewitz explains the importance of this method of agile development and how the use static analysis of code bases can help the "hard sell" of intentional architecture to management.
Etsy's approach to big data has been to give the entire organization visibility to different sources of data generated by their product as well as access to the experts who know how to use it. Nell Thomas explains her role at Etsy and how Etsy's view of big data has shaped its product's evolution.
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.