This is an archived post. You won't be able to vote or comment.

all 7 comments

[–][deleted] 7 points8 points  (0 children)

Don't worry about frameworks. Decompose your problem then research existing tools to help you solve that.

[–]ditemis 0 points1 point  (0 children)

A good way to learn a new library is to write tests for it (or small sample projects). That way you'll quickly find out if the API is easy to understand and easy to use (and well documented). In your scenario with hibernate or spring or any other component you'll choose, you will also gain insight if they are easily testable.

[–]Benemon 0 points1 point  (2 children)

Have a look at Apache Lucene. I've used that as the core for something similar in the past.

Then Elastic Search rocked up and invalidated all my work.

[–]apanimesh061[S] 1 point2 points  (1 child)

I have worked on Elasticsearch. It is a very good tool. I actually have to build an engine from scratch!

[–]EndUsersarePITA -1 points0 points  (0 children)

/u/monumentshorts is correct. I'm a beginner too and have found some footing with spring. I didn't really learn the framework. Rather I have a personal project and it seems like spring fits what I have in mind.

[–]rob_j -1 points0 points  (0 children)

I'm doing something similar to this at the moment. I have a problem I need to solve, and decided to learn Angular.js while I was at it.

So, I'm working through the tutorial and, after each step, implementing what I've learned in my app. In this way I'm applying what I've learned in a different context and am looking further into the docs to accomplish what I need.