- Taschenbuch: 74 Seiten
- Verlag: O'Reilly and Associates; Auflage: 1 (22. Juni 2012)
- Sprache: Englisch
- ISBN-10: 1449328385
- ISBN-13: 978-1449328382
- Größe und/oder Gewicht: 17,8 x 0,4 x 23,3 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 1.025.338 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Andere Verkäufer auf Amazon
Just Spring Data Access (Englisch) Taschenbuch – 22. Juni 2012
|Neu ab||Gebraucht ab|
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Über den Autor und weitere Mitwirkende
Madhusudhan Konda is an experienced Java consultant working in London, primarily with investment banks and financial organizations. Having worked in enterprise and core Java for the last 12 years, his interests lie in distributed, multi-threaded, n-tier scalable, and extensible architectures. He is experienced in designing and developing high-frequency and low-latency application architectures. He enjoys writing technical papers and is interested in mentoring.
|5 Sterne (0%)|
|4 Sterne (0%)|
|3 Sterne (0%)|
|2 Sterne (0%)|
|1 Stern (0%)|
Die hilfreichsten Kundenrezensionen auf Amazon.com
I feel that the author did a good job with the sample code that he walks through in order to explain how to setup and work with the different data access protocols. I also enjoyed the fact that he explained that there is a better way of writing your code when dealing with Spring version 3 or later that you should just work with the native APIs of the protocols and allow Spring to handle the dependency injection. I felt that this was good information to have and to understand when creating your own implementation. There was one section in Chapter 5 that I wish the author would have explained or elaborated on in more detail and that was the JDO versus JPA versus Hibernate implementations. Personally, I think this is a critical area for any architect to understand before selecting the implementation that they want to use in their application. The author does provide some information on the pros and cons, but the section is limited to 2 pages and after reading the section I felt like I still had questions. For example, the author states that if you are going to deal with different data source from Relational Data Bases (RDB), object databases, XML, etc., that you will want to use JDO; but then he states that you could use JPA with a change to make it work with non-RDB data source and doesn't say how. I really wanted to know how, therefore I wish that this section provided a bit more depth in it coverage of the topic.