New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on May 25, 2009
In this presentation recorded at QCon SF 2008, Jeremy D. Miller shares lessons learned while developing a project over 5 years. He talks about his mistakes, what to avoid and how to design, code and test better.
Watch: The Joys and Pains of a Long Lived Codebase (1h)
Miller gives actual code examples from StructureMap, an Inversion of Control / Dependency Injection tool for .Net that he created. The coding lessons include:
- Avoid the string representation of a type instead of the type itself.
- Breaking encapsulation is really bad.
- Avoid bloated code.
- Noun-based design is naïve. Rather use design abstractions by responsibilities and roles.
- Create a test fixture per behavior.
- Advices for creating usable frameworks and good API.
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
Agility at scale, become as agile as you can be
Getting Started with Stratos - an Open Source Cloud Platform
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
No comments
Watch Thread Reply