Showing posts with label Application. Show all posts
Showing posts with label Application. Show all posts

Tuesday, January 18, 2011

Why Choose Groovy and Grails for Web Application Development?

Grails is a Rapid Application Development web framework inspired from Ruby on Rails. Grails runs on Java's Virtual Machine (JVM) and relies on Groovy - a JVM compatible language. Grails is one of the fastest growing RAD (Rapid Application Development) web frameworks.

Grails provides a no ceremony, Convention over Configuration framework that increases the developer's productivity by multiple times.

Grails

In a traditional Java project, one spends weeks writing the initial code to set up the infrastructure but that can be done in a matter of couple of hours with Groovy and Grails. The Speed and Productivity that it gives you is incredible. Development with Grails is not like traditional Java development. Some of the advantages that are associated with Grails are scaffolding, auto reloading of classes (change code, click refresh in browser to see the change), unparalleled testing support, and GORM - greatest of all database abstraction layers.

Grails has provided a solid solution to Java community who can now develop applications with the speed of Rails and at the same time capitalize on the robustness of Java.

Grails follows a DRY (Do Not Repeat Yourself) principle which enables an accommodation of requirements changes with a breeze. Extensive plugins (there are around 500 plugins), vibrant Grails community & extensive online documentation is a big plus and helps developers not to get stuck on any issue for more than a few hours. Its intuitiveness helps speed up the productivity of team members new to Grails framework.

Grails is now being used by companies such as LinkedIn, Pepsi, Wired.com, Sky.com, Aegeon etc.

There is no denying the fact that current adoption of Grails is nowhere near to Rails or Django, leading RAD web frameworks but at the same time, growth of Grails is astonishing.

Grails is now in the making of a main stream technology & RoR of Java world. G2One, the company behind Groovy and Grails was acquired by SpringSource in Nov 2008 and SpringSource was later acquired by VMware which speaks volumes about the growth and importance of Groovy and Grails.

Why Choose Groovy and Grails for Web Application Development?

Iphone Programming PDF Know Oracle SQL Android PDF

Wednesday, January 12, 2011

Traditional and Web Application Testing

There are several components of traditional application testing that can be used in the web testing process because of best practices along with the probability that traditional systems may be supporting the web system in the background. Some of the components of traditional testing that can be used in Web testing include checking its function and performance in regards to accessibility and reliability.

In testing of Web systems, one has to check functionality using all browser variants to ensure consistency in its display and navigation across the various platforms. Due to the nature of Web systems, there is also the issue of network infrastructure capacity and compatibility which would have an impact on both functionality and performance.

Grails

As an example, if the Web system includes audio or video feeds, then there will be a requirement for quality of service (QOS) functionality within the network infrastructure equipment and the ability to appropriately burst bandwidth allowances when required due to traffic loads. Without QOS functionality in these areas, the Web system may not function as designed from the end user perspective, because the multimedia stream is subjected to jitter, latency, or both. In traditional systems these concerns were limited to the constraints of the CPU, memory and other internal hardware components. Although this example walks a fine line between functionality and performance, sometimes the difference between them is only a matter of perspective.

One type of testing that if overlooked that could have a detrimental effect on functionality and performance is security testing. Although security testing is occasionally performed, depending on the particular design, in a traditional systems environment, it should be mandatory for Web systems due to the effects on confidentiality, integrity, and availability of these customer facing and back-end systems. An attacker could find a way to take control of the administration, performance, and functionality of a Web system. One small example would be having a website defaced...it would be a public embarrassment to any business and even more troubling if it causes a loss of income due to customer loss of confidence in the organization.

The complexity and criticality of Web systems absolutely requires due diligence in the exercise of its testing and that has been the inspiration to adapt traditional testing techniques and go several steps further.

Traditional and Web Application Testing

Iphone Programming PDF Android Development Guide