Petabyte

Using Node.js you can write a web server in as little as six lines of code. Here is a variation for the sample from the Node.js  (Node.js Synopsis) //Imports the http library var = require(http); http.createServer(function(request, response){     response.writeHead(200,{'Content-Type':'text/plain'});     response.end('Hello World\n'); }).listen(8124); console.log('Server running at http://127.0.0.1:8124/'); I was asking myself why would i want a server side javascript (which is the whole idea of Node.js) ? Besides that it uses a non-blocking I/O model (this means that other processing can continue if it does not depend fro an I/O to complete, kind of like an asynchronous call to perform the I/O) . One use case that i can think of is that  I can wrap other services (e.g. other source of data like json/xml)  specially ones that are exposed as web service APIs (e.g. Google APIs).

The Future When dealing with concurrent processing, starting Java 1.5 the 'Future' looks bright. In java 1.5 it is now easier to collect results from asynchronous processes by getting the future. Here are the objects that you are going to need to process concurrently and collect results from those concurrent processes: //Please refer the the Java API documentation on how to properly instantiate the objects below //This is just to give an overview on how they are used together and relate to each other. //A ThreadPoolExecutor is basically a pool of threads that you configure that will asynchronously //perform the tasks that you provide it ThreadPoolExecutor threadPoolExecutor = new ThreadPoolExecutor(); //A completion service is the object that collects the results of the task that the ThreadPoolExecutor //completes. That is why when you instantiate it you need to pass it a ThreadPoolExecutor. CompletionService completionService = new ExecutorCompletionService (th

MyGeekBall iPhone App Here is the latest myGeekBall app. It is a simple app that i created to learn the ins and outs of creating an iPhone app. Did you know that all applications are reviewed by Apple ? Their reason is to protect consumers from malicious app.  Please download and enjoy the new App!

The term "software engineering" was coined 42 years ago. Software Engineering is defined as the systematic approach to development, operation, maintenance, and retirement of software (IEEE). Another definition is the practical application of scientific (systematized body of) knowledge and construction of computer programs and associated documentation required to develop, operate and maintain them (Boehm) One of the areas of software engineering that foster quality to a software product is design. Software design is the place where we can access models, diagrams of a logical product for quality. Adhering to industry accepted design practices is a must in order to produce quality software products. It is good to adhere to sound software design guides like cohesion.  Software engineers who wanted to write quality software uses proven principles for software design. The idea of cohesion and coupling in software design has been around for decades. It has been measured as a q

Trying out Google+, so far i like the 'Circles' Thanks to Kathryn Mcconnachie  of IT Web (South Africa) 

Spring Source Tool Suite  Using STS inside the companies firewall Go to Window > Preference > Maven > User Settings Take note of the location of settings.xml If it does not exists, create a new one Add the element below in the file (Use the proxy that your company uses) Change the host and port to the details that is particular to your company's proxy setting Make sure to add user name and password if you need to aunthenticate.

N-Tier systems can also yield high performance. They can be highly optimized at each tier. Server clusters can be used where bottlenecks are encountered, connection pools can be used by applications to acquire and release connections (a process more effective that creation and destruction of connections) and so on. Though not relevant to the discussion it should be noted that putting all business rules in the database tier reduces database portability and also violates tier encapsulation. Hence it is not considered a J2EE best practice to use stored procedures and triggers extensively for business logic processing.(from about.com ) Business rules in stored procedures reduces portability and violates tier encapsulation. Another thing that i experience with this is that usually the business logic gets split between the business tier and the stored procedure because the stored procedure can not do the all the complex processing that a business logic requires.