April 2008

Monthly Archives

New SDO Tutorial

New SDO Tutorial

We have published a new SDO tutorial that provides a general introduction to SDO (rather than being product-specific).

Labels:


Scalability and Innovation

Scalability and Innovation

It’s a common misconception that Google’s key intellectual property is its seemingly unique ability to delivery accurate search results. In fact, the patent for the famous PageRank algorithm is owned by Stanford University. Google listed the scalability of its vast infrastructure as its key asset during its Initial Public Offering.Tim O’Reilly has explained that “it’s not accident that Google’s system administration, networking, and load balancing techniques are perhaps even more closely guarded secrets than their search algorithms.”

The business value of this infrastructure is discussed in this month’s Harvard Business Review (HBR) in a detailed article about Google innovation called “Reverse Engineering Google’s Innovation Machine”.

HBR explains:

Google has spent billions of dollars creating its Internet-based operating platform and developing proprietary technology that allows the company to rapidly develop and roll out new services of its own or its partners’ devising.

However, Google not only has infrastructure that allows it to add new on-line services quicker and easier than its competitors, it also has a management strategy that encourages staff to innovate by including it in job descriptions:

Much of what the company does is rooted in its legendary IT infrastructure, but technology and strategy at Google are inseparable and mutually permeable – making it hard to say whether technology is the DNS of its strategy or the other way around.

What would it mean for your organization if there were sufficient infrastructure resources to allow everyone to experiment with new ideas?


Spring Versus EJB

Spring Versus EJB

JavaLobby has published an interesting article on job trends for Spring versus EJB. It appears that the job market for Spring jobs – and therefore commercial Spring development – is accelerating.


Optimizing the Slowest Thing

Optimizing the Slowest Thing

Today’s InfoWorld Off The Record proposes that improving the performance of any application starts with optimizing the slowest thing. The stories are from 40 years ago. Nowadays, almost every business application uses a database and it is almost always the database that is the bottleneck. With the speed of multi-core processors, only exceptionally complex business logic could possibly take longer than even simple database reads or writes.So that means that the rule “Optimizing the Slowest Thing” means database optimization. This is why CodeFutures is rolling out a free database performance analysis service, starting with MySQL.

The elements of the performance analysis are:

-MySQL configuration analysis
-Strategies for database reorganization and optimization
-How to perform database optimization without taking your application down
-Database size optimization (reclaiming unused disk space)
-Long-running query analysis
-Indexing strategy
-Reliability/availability/failover evaluation

CodeFutures has already developed a tool to gather the necessary information about a specific MySQL deployment. At the moment, the data analysis is manual. The tool will eventually evolve to include features providing immediate performance and configuration feedback. However, full analysis of the data requires someone with significant MySQL optimization experience – so there will always be a limit to what a tool can do.

You can your request free MySQL performance analysis here.


install4j 4.1 Launched

install4j 4.1 Launched

The new version of install4j, the installer used with FireStorm/DAO, is available. You can read about the new features here. ej-technologies has done an excellent job as usual.