[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 293
  • Last Modified:

J2EE QoS

The J2EE specifications never dictate the quality-of-service levels to be provided by their implementations, for instance in terms of performance or availability. Why not?
0
DrAske
Asked:
DrAske
1 Solution
 
JaaxCommented:
I am not sure if JCR has not laid down any QoS accompanying J2EE specs. But I personally, I against it for the following reasons-

-Defining a consistent QoS for a web application is easier said than done. Because a lot of uncontrollable parameters like network connectivity and hardware configurations at remote server - name a couple of them - would creep into the perceived measurement of quality and yields different level of user satisfaction for the same functionality. This would inevitably lead to define QoS on each and every hardware component - this beats the very purpose of Java being professed as platform independent
-If the QoS standards are unreasonably high, they may limit the no. of vendors offering reliable and predictable services. This might cause friction between vendors and JCR.
-And most importantly, ratifying and enforcing these QoS is another herculean task in itself. This will sprout many accrediting softwares purporting to gauge the performance. Someone needs to ratify these accrediting softwares as well.
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now