What is the difference between EJB, hibernate, spring and JSF?

• JSF: a GUI framework - you don't need this if you only want to implement a backend
• EJB: a standard for distributed components, used to be horribly complex, but version 3 of the standard is quite easy to use. This could be part of your solution.
• Hibernate: An Object-relational mapping framework. It served as the inspiration for the JPA (Java Persistence Architecture) standard, which is now supported by both Hibernate and EJBs.
• Spring: An application framework that does all kinds of things, among them dependency injection, web GUIs and AOP.

However, if you want to do REST, then the most important standard for you is JAX-RS. You can use it either within the Spring framework or with EJBs. For persistence, you could use Hibernate, or the JPA implementation of an EJB container such as Glassfish

These are frameworks for different layers.

• JSF is for the view (web) layer, it's a component oriented framework (every part of a page is a component, it has state) like Wicket or Tapestry, and unlike Action frameworks like Spring MVC, Struts or Stripes

  Books: Core JavaServer Faces (3rd Edition)
  Tutorials: CoreServlets.com

• EJB 3.x is a container that's part of the JavaEE stack. It does things like dependency injection and bean lifecycle management. You usually need a full JavaEE application server for EJB3

  Tutorials: JavaEE 6 Tutorial: EJB
  Books: EJB 3 in Action

• Spring is also a container, but Spring can run in any java code (a simple main class, an applet, a web app or a JavaEE enterprise app). Spring can do almost everything EJB can do and a lot more, but I'd say it's most famous for dependency injection and non-intrusive transaction management

  Online Reference (excellent)
  Books: I couldn't find a good english book on Spring 3.x, although several are in the making

• Hibernate was the first big ORM (Object relational mapper) on the Java Platform, and as such has greatly inspired JPA (which is part of the EJB3 standard but can be used without an EJB container). I would suggest coding against JPA and only using hibernate as a provider, that way you can easily switch to EclipseLink etc.

  Books: Pro JPA 2: Mastering the Java™ Persistence API (not hibernate-specific),
  Java Persistence with Hibernate (getting a bit old)