Transactions without Transactions
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Getting Started with Stratos - an Open Source Cloud Platform
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
18 agile and lean practices for effective software development governance
I see nothing new. The only difference between today's Lego 'parts' and those of the future described, is that today they are much smaller - typically statements in some programming language at the lowest level of abstraction, or invocations of some framework function at a slightly higher level of abstraction. We will always be faced with the task of finding the appropriate parts and connecting them...
That's because we are actually giving the finishing touches on a paradigm-shifting development methodology that resembles the Lego Hypothesis. And its basic building block is called an atom, just like in Noble's presentation.
The Lego Hypothesis will be proven right, but probably sooner than James Noble expects. Fingers crossed!
While there are forking and duplicate projects, a typical Linux distro today is built together with large collection of softwares and libraries that has been picked and hacked together to become a working OS. So I guess this is also one example of Lego building blocks.
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.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
3 comments
Watch Thread Reply