InfoQ Homepage Conferences Content on InfoQ
-
Just Do It: Migrating to Grails
Emiliano Conde shares the process, tools, and lessons learned migrating jBilling.com from Struts/EJB to Grails/Spring.
-
Clojure in the Wild Web–7 Reflections
Ignacio Thayer shares his team’s experience working with Clojure, some of the problems encountered, and provides advice for a faster development cycle.
-
Running with the Devil: Mechanical Sympathetic Networking
Todd Montgomery discusses messaging: application level batching, UDP datagram size’s impact on performance, sendmmsg/recvmmsg, implementing asynchronous calls.
-
Polyglot Web Development With Grails 2
Jeff Brown discusses how Grails enables polyglot web development, with a focus on Scala and Clojure, and explains what it takes to add support for new languages.
-
Enabling Collective Improvisation in Agile Software Development
Adrian Cho discusses applying Jazz performance principles to software development: managing friction, the importance of awareness, diversity, health, and leading on demand, embrace change and conflict
-
Visualizing Java Garbage Collection
Ben Evans discusses garbage collection in Java along with some tooling for understanding and visualizing how it works.
-
When Geek Leaks
Neal Ford keynotes on the impact the real world has on software development and the other way around.
-
API Business Models. 20 Models in 20 Minutes
John Musser presents 20 API business models explaining how developers can make money with their APIs.
-
Functional Reactive Programming in the Netflix API
Ben Christensen describes how Neflix has optimized their API using a functional reactive programming (modeled after Rx) in a polyglot Java stack.
-
Under the Hood: Using Spring in Grails
Burt Beckwith introduces Spring development to Grails developers.
-
The Structure of API Revolutions
Daniel Jacobson shares advice on dealing with evolving APIs based on his experience with Netflix APIs.
-
Riak and Dynamo, Five Years Later
Andy Gross reflects on five years of involvement with Riak and distributed databases and discusses what went right, what went wrong, and what the next five years may hold for Riak.