Reputation: 9198
I'm new to this, so, sorry if I'm wrong.
Upvotes: 5
Views: 1719
Reputation: 23587
Well there are ways to have some performance tips both at database levels and Application levels.
For database levels here are few inputs
For some ORM layers like hibernate
it also provides some sort of mechanism to cache the outputs in primary levels and secondary levels.
For application levels we have many options few of them are
here is a complete list of java based caching frameworks
and some googling will help you to find many other options for UI layers there are lots of area of improvements like
Yahoo has very good blog for this.YSLOW from YAHOO.If you are in the early stage of development i will suggest not to go for them as they lead to premature optimization and can lead to may problems.
Upvotes: 7
Reputation: 915
Frameworks exist for this purpose and Ehcache is one of them. Here you can read up on how you can use it:ehcache
Upvotes: 3
Reputation: 8513
Unfortunately, the question is way too broad (there are books on the topic, so it literally falls in the FAQ definition of offtopic)—and thus is likely to be closed soon.
In brief, there are plenty of Java caching solutions, including for example Guava and ehcache.
The three best techniques would be:
First, before changing anything, second, to make sure your changes have effect, third time in production, to make sure your changes do work in real life.
On the levels—both, the decision depends on the profiling data.
Upvotes: 2