A Comparison between EJB and COM+ Business Components, Case Study: Response Time and Scalability
| dc.contributor.author | Abu-Kamel, Abedulhaq | |
| dc.contributor.author | Zaghal, Raid | |
| dc.contributor.author | Hamed, Osama | |
| dc.date.accessioned | 2018-09-16T10:49:30Z | |
| dc.date.available | 2018-09-16T10:49:30Z | |
| dc.date.issued | 2010-01-08 | |
| dc.description.abstract | Most distributed system architectures are designed as a three-tier systems consisting of a thin-client, middleware and a database. The overall performance of such systems depends on the performance of each tier individually and the overhead incurred by the collaboration between these three tiers. Nowadays, the two most popular middleware systems are: Microsoft’s .NET platform and Sun’s Java 2 Enterprise Edition (J2EE) platform. In J2EE, the middle tier infrastructure is called Enterprise JavaBeans (EJB) and in the .NET framework, it is called Component-Oriented Middle-Tier (COM+). Usually, the middle tier provides the business logic (any code that is not specifically related to storing and retrieving data, or formatting data for display to the user) and the performance of this tier is crucial to the overall performance of the distributed system. | en_US |
| dc.identifier.issn | 1865-0929 | |
| dc.identifier.uri | https://dspace.alquds.edu/handle/20.500.12213/921 | |
| dc.language.iso | en_US | en_US |
| dc.publisher | Springer | en_US |
| dc.title | A Comparison between EJB and COM+ Business Components, Case Study: Response Time and Scalability | en_US |
| dc.type | Article | en_US |