10 tips on how to prevent business value risk
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.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Floyd Marinescu on Nov 10, 2006
A firestorm was set off on a TSS thread about a slide from Tim Bray's keynote at a PHP conference with a bar graph showing PHP more scalable than Java. Tim Bray has since put the slide in context in a comparison intrinsic qualities of Java, Rails, and PHP on his blog, as well giving InfoQ his own personal take on it. The context for the discussion is Web Application Building, which Tim characterizes as a problem space in which "we are not considering general issues of compute performance, because in Web apps, you don’t do much computing. You get some values from the browser, you use them to pull some info out of a database, you report them to the user, maybe you update the database, and that’s about it."Mostly because there's less code. The fact that Ruby *forces* MVC on you helps too, also the fact that the templating and ORM and testing and application code are all so tightly integrated helps. Bear in mind that we still don't know how well Rails is going to work outside of the CRUD-centered greenfield app space where it shines.InfoQ: Why is PHP more scalable than Java?
It isn't, but in the Web-app space, it's a little easier to scale (shared-nothing by default); Java requires you to think.InfoQ: So which intrinsic is more important to you?
For me, maintainability; but I'm sure there are lots of other people who would make different choices for very good reasons.Tim also explained the maintainability point further on his blog:
Out there in the wild woolly “Web 2.0” world, maybe getting it built quick is all that matters, because after you’ve knocked ’em dead and been acquired, you can use the money from the Yahoo! buy-out to rebuild everything right the second time. In the enterprise though, I kind of suspect that smart developers and smart managers know that for real apps, the big development cost starts to happen after they’re delivered.You can also see Tim Bray on InfoQ's video interview with him on Rails, Rest, Java, and XML.
Monitor your Production Java App - includes JMX! Low Overhead - Free download
18 agile and lean practices for effective software development governance
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
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.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
No comments
Watch Thread Reply