Event-driven architecture (EDA) is a push-based communication between publisher and consumer, which predominantly use for proactive notification in real time environment.
For e.g. Fraud notification from credit card Company, shipping, order fulfillment etc.
EDA use to communicate with consumer with minimum or no delay and avoid busy-wait thread stats. Continue reading
Today’s application expects access of all business in enterprise environment regardless of application technologies, which require, seamless integration with desperate systems.
This integration can be achieved through wiring of desperate systems using Middleware technologies. Continue reading
In this article I’ll introduce the basic coding that require to create JQuery DataTable using JSON passed by simple servlet.
DataTable is very powerful JQuery based grid with advance features which can be build in short span of time with customize features. Continue reading
Agile mythology has small box iterations rather than phases. The output of each iteration will be production release deliverable and could be evaluate and get early feedback. Agile development need continuous enhancement in development process to improve software quality which keep improving businesses and their goal. Continue reading
I discussed about RESTful architecture consideration and how to build RESTful web services using Jersey JAX-RS [JSR 311] in JAVA. Today I am going to discuss how to build the RESTful web services using Grails framework.
GRAILs framework is the platform which provides end to end solution to build web application from scratch to advance intuitive RIA web application. Grails potentially be a one-stop shop for all your enterprise application development. Grails is modular, allowing you to pick and choose which modules are applicable for your application Continue reading
I have discussed my earlier article about architectural consideration on RESTful system for distributed environment. This article we are going to discuss how to build RESTful web services with Jersey and Apache Tomcat. Continue reading
REST comes from Roy Fielding’s PhD paper, published in 2000, and it stands for Representational state Transfer. REST is set of architectural constrains which can apply on application design to make application more scalable, flexible, reusable, loose couple and align to business agile. Fielding’s REST guideline defines the specific role for data, component, operation, communication protocols, data consumer and producer.
REST is generic constraints for distributed technologies with no limits of technologies or stack.
Following are the constraints that define a RESTful system.
- Should be for distributed system
- Data communication should be stateless
- Request should be independent and reusable
- It has to support caching.
- System should be access uniformly accessible
- Desperate representation of response
- Standardize operations
These are independent of technology and represents how data communicate between and what’s guideline need to follow during data transfer between distributed systems.
e.g. Static web is RESTful as it follows fielding’s key guideline on REST. For instance, the existing static web provide caching, stateless connection, the unique link to resources (HTML). On the other hand, traditional dynamic web applications haven’t always been RESTful, because they typically break some of the outlined constraints. For instance most dynamic application is not stateless.
But we can use abstraction on dynamic system that makes a RESTful system using HTTP protocols, URIs, representation and resources.