• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

J2EE core patterns used for nfr

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is not clear for me the use of J2EE core patterns for meet non functional requirements.

It seems to me that using core patterns one obtains layer of abstractions, more elegant design, but ...
.. does core patterns help to improve NFRs?

Which core patterns help to improve availability?
Which core patterns help to improve performance?

Thanks
 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I dont think, just by implementing design patterns, we can address NFRs. Though in case of Performance I can definitely have my class diagram following proper J2EE design patterns like session facade, or service locator caching home/remote references to avoid multiple lookups but that will not be enough.

What I would do instead is as follows:

Performance
Class Diagram:
1> Draw class diagram following J2EE design patterns [as given above]
2> Display some specific performance monitoring classes like Aspect Oriented Programming classes for performance and then comment on how they help segregate the code and help improve performance.
3> Talk about how performance test will be perform simulating production load in testing environments to identify performance bottlenecks before code reaching production.

Availability:
Deployment diagram:
1> Draw deployment diagram with multiple instances of servers balanced by load balancer.
2> Draw failover nodes.
2> Draw other clustered back end environment.
3> Talk about how the hot fix process will be set to perform rolling bounce of production servers [bouncing servers one after the other and not bounce everything together] to have 24*7 availability.

I think NFRs have to be managed by software and hardware changes and not just one alone.
 
My pie came with a little toothpic holding up this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic