Practical API Design
Confessions of a Java Framework Architect
Published on 23. December 2014
Book
Paperback/Softback
XXVII, 387 pages
978-1-4302-1172-3 (ISBN)
Description
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
More details
Edition
First Edition
Language
English
Place of publication
Berkeley
United States
Publishing group
Springer-Verlag Berlin and Heidelberg GmbH & Co. KG
Target group
Popular/general
Illustrations
XXVII, 387 p.
Dimensions
Height: 235 mm
Width: 191 mm
Thickness: 23 mm
Weight
773 gr
ISBN-13
978-1-4302-1172-3 (9781430211723)
DOI
10.1007/978-1-4302-0974-4
Schweitzer Classification
Other editions
Additional editions
E-Book
09/2008
APress
€58.84
Available for download
Book
07/2008
APress
€80.24
Shipment within 15-20 days
Person
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.
Content
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.