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 Hartmut Wilms on Mar 11, 2007
Edward Bakker and Jezz Santos have been writing a very interesting series about Software Factories, which goes way beyond the basics. Lately the series has come to an end and now provides a complete set of concise guidelines. The Microsoft Software Factories Initiative and Domain-Specific Languages have been a cause of many discussions long before any implementations were available. Today, Microsoft provides tools such as the Guidance Automation Extensions (GAX), the Guidance Automation Toolkit (GAT), and the Domain-Specific Language Tools (DSL Tools).
The tools allow developers and architects using the Software Factories provided by the Microsoft patterns & practices team as well as building Factories on their own. Altough many resources are available, it is still very difficult to enter the world of Software factories. The 201 series is a great way to start. As Edward Bakker points outIt might sound simple; install GAT and the DSL Tools and build your first factory but unfortunately, from what I experienced, it isn't that easy (it might be me of course!). I had (and still have) a lot of questions like for example: "What is a software factory", "When would you build one", "How would you build one", "What tools would you use" and many, many more.The series elaborates on a wide variety of aspects, which developers and architects have to deal with when using or building Software Factories:
Factories 201 Series - Building Software FactoriesThe issues are discussing the meaning of Software Factories, when to use or build one, how to integrate factories into your development cycle and IT-Governance and what challenges are to expect and how to cope with them.
- What are they (concretely)? (Edward)
- When would you build one? (Jezz)
- What do I tell my Manager? (Edward)
- How long will it take? (Jezz)
- What would you build? (Jezz)
- With what would you build it? (Edward)
- How would you build it? (Jezz)
- What should you strive for? (Edward)
- What are the challenges? (Jezz)
This series was created in a format that asks a logical sequence of questions that you might have when trying to figure out how to build software factories today. We have covered many such issues as they arose and shared much of the combined knowledge and experiences built up over the last few years in this space.
Whether you like or dislike the idea of Software Factories, you should take a look at this series.
A Guide to Branching and Merging Patterns
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Getting Started with Stratos - an Open Source Cloud Platform
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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