Tim Berglund
Tim Berglund runs a software consulting firm called the August Technology Group, which provides training and development services to customers building web applications with open-source tools, especially with the Grails framework. His technology interests span web applications, business integration, data architecture, and software architecture, but his greatest passion is to help developers improve in their craft. He is a speaker internationally and at user groups in the United States, and helps lead IASA Denver and the Denver Open Source User Group. He is currently writing the book, Deploying Grails (to be published by O'Reilly), due out in 2010. He lives in Littleton, CO, USA with his wife and three children.
Track abstract - Emerging Technologies/Cloud Computing
Managing Grails with JMX
Grails has enabled your team to achieve productivity levels you never knew possible for web applications on the JVM. Now that you’re deploying real applications inside your enterprise, you’d better equip them with the kind of production-class monitoring and control capabilities that will endear you to the operations team like never before. Learn how to instrument key Grails configuration data structures with JMX, and control and monitor other parts of your Grails app with this standard Enterprise Java technology. See who’s logged in and what the database connection pool is doing. Dynamically change parameters in Config.groovy. Trend response times and gather stats on key integration points. Take control of your Grails app!
Track abstract - Conversation Corner
The Dire Need for Encryption in Webapps
This fishbowl will initially contain Matthew McCullough and Tim Berglund.
An informal study shows as many as 70% of today's public facing web apps are not using hashing of passwords and are storing customer data in the clear. As professional engineers, we need to step up to our responsibility to secure customer information. In this fishbowl, we'll discuss approaches being taken to encryption on the wire, in the DB and on disk. This can have implications all the way back to domain driven design and separation of concerns. We'll solicit inputs on what folks at the conference are struggling with in this area, why encryption usage is so rare, and what we can do as thought-leaders to increase customer data security in our applications.
The idea with a fishbowl discussion is that you have 5 chairs, you may only speak when you sit on a chair, and one must be empty at all times. If someone sits on the last chair, someone else must get up. The chairs are initially occupied by two or three of the conference speakers, to get the discussion going. Other conference participants are encouraged to join in by sitting on an empty chair. Anyone sitting in the fishbowl who finds they no longer have anything they really want to say, should consider giving up their place.
