DIVIDE AND RULE
Technologies are changing in a rapid pace in today’s world. Tying business logic tightly to other application components like the user interface, for example, deeply impacts existing systems whenever there comes a question of technology upgradation in any of the components’ scope. Just a couple of years back, software editors for Web applications could prefer from servlets and JSPs, struts, and perhaps XML/XSL. Now AJAX has gained a strong popularity over Tiles and Faces that came in focus in between. It would be a ridiculous decision to redevelop an application's core business logic every time the component specific preferred technology changes. Answer to this common challenge in software development that we practice in IdeationTS is to simply adopt the division of labor strategy in application architecture design; and yes, it is the Model-View-Controller (MVC) design pattern that comes as no. one choice in this scenario to address such problems by modularizing applications based on responsibilities and maintaining a balance in distribution of overhead among modules.
- The Model, often by using Enterprise JavaBeans™ or plain old Java objects (POJO) to take care of business logic.
- The View, responsible for presentation of the user interface.
- The Controller, usually implemented with Java servlets and/or associated classes, for application navigation.
We have a Java EE technology development team, which includes very proficient, extensively experienced technical architects and programmers. This team has been successfully developing applications, on Java/Java EE platforms, right from ecommerce, enterprise solutions to the current trends that include Web 2.0 and Cloud Computing, Distributed Applications to provide solutions across various business domains. We leverage our technical expertise and domain knowledge to develop and deliver advanced, state-of-the-art, effective and cost-effective solutions to address today’s enterprise needs.
Ideation Technology Solutions develops systems both internally at IdeationTS as well as for our customers or partners. We choose to standardize on Java EE to ensure consistency throughout a large number of systems in terms of architectural approach. Our regular technology review initiatives focus on how Java EE applications can take advantage of most of the practical benefits of micro-services without the added complexity. The applications use a mix of WildFly and JBoss EAP along with other JBoss ecosystem projects like Hibernate Envers, Hibernate Search, and Drools. The applications also used ICEfaces and PrimeFaces.