Richard Chesterwood wrote:
Runrioter Wung wrote:Before I mainly used Hibernate in my project. I know that now Hibernate will become an implement to JPA. I need a book to refer to for studying. So I wonder which one is better.Give me reasons.Thank you.
If you know Hibernate already and you've used it extensively, it's possible that you don't need much to switch to JPA. You could certainly get by skimming through a book - even the knowledge that Session becomes EntityManager, and SessionFactory becomes EntityManagerFactory will get you a lot of the way there! Especially if you've been using the annotations for your hibernate mapping - for many years now the Hibernate Annotations have actually been the JPA annotations.
So it's quite possible you don't need a book or a course.....
Mike Cantelon wrote:
Node.js is great for applications that require high concurrency and minimal CPU/memory usage. So things that should feel "real-time" like online games, chat, and web applications. For a balanced look at what use-cases Node.js is most suitable for, I recommend Chris Richardson's talk "Node.JS: The Good Parts? A Skeptic's View" (https://www.youtube.com/watch?v=CN0jTnSROsk).
If you need part of your application to be sequential, you can a technique called "flow control". Flow control makes asynchronous logic behave in a synchronous fashion. You can either implement flow control yourself in your application or, much easier, simply use flow control modules. One such flow control module is async (https://github.com/caolan/async).
Saif Asif wrote:oh thats great ! What exactly was the issue ?