Jaroslav Tulach

Practical API Design

Confessions of a Java Framework Architect

• Broschiertes Buch

Produktbeschreibung

Now available in paperback-

You might think more than enough design books exist in the programming world already. In fact, there are so many that it makes sense to ask why you would read yet another. Is there really a need for yet another design book? In fact, there is a greater need than ever before, and Practical API Design: Confessions of a Java Framework Architect fills that need!

Teaches you how to write an API that will stand the test of time Written by the designer of the NetBeans API at Sun Technologies Based on best practices, scalability, and API design patterns

Produktdetails

• Verlag: Apress / Springer, Berlin
• Artikelnr. des Verlages: 978-1-4302-4317-5
• 1st ed.
• Seitenzahl: 416
• Erscheinungstermin: 7. Juni 2012
• Englisch
• Abmessung: 235mm x 191mm x 23mm
• Gewicht: 713g
• ISBN-13: 9781430243175
• ISBN-10: 1430243171
• Artikelnr.: 34761462

Autorenporträt

Jaroslav Tulach is the founder and initial architect of NetBeans, later acquired by Sun Technologies. As creator of the technology behind NetBeans, he is still with the project to find ways to improve the design skills among all the programmers who contribute to the success of NetBeans open source project.

Inhaltsangabe

1. The Art of Building Modern Software
2. The Motivation to Create an API
3. Determining What Makes a Good API
4. Ever-Changing Targets
5. Do Not Expose More Than You Want
6. Code Against Interfaces, Not Implementations
7. Use Modular Architecture
8. Separate APIs for Clients and Providers
9. Keep Testability in Mind
10. Cooperating with Other APIs
11. Runtime Aspects of APIs
12. Declarative Programming
13. Extreme Advice Considered Harmful
14. Paradoxes of API Design
15. Evolving the API Universe
16. Teamwork
17. Using Games to Improve API Design Skills
18. Extensible Visitor Pattern Case Study
19. End-of-Life Procedures  

---

Theory and Justification.- The Art of Building Modern Software.- The Motivation to Create an API.- Determining What Makes a Good API.- Ever-Changing Targets.- Practical Design.- Do Not Expose More Than You Want.- Code Against Interfaces, Not Implementations.- Use Modular Architecture.- Separate APIs for Clients and Providers.- Keep Testability in Mind.- Cooperating with other APIs.- Runtime Aspects of APIs.- Declarative Programming.- Daily Life.- Extreme Advice Considered Harmful.- Paradoxes of API Design.- Evolving the API Universe.- Teamwork.- Using Games to Improve API Design Skills.- Extensible Visitor Pattern Case Study.- End-of-Life Procedures.- Epilogue.- The Future.