Jason Schadewald is Product Manager for Language Products at Parasoft, the leader in software defect prevention technology, software quality process intelligence, and development testing. With an eye toward finding optimal, sustainable, long-term solutions, he applies a critical mind and formal methods to all aspects of software development, testing, and delivery – mitigating risks by resolving ambiguities at the earliest possible stages. He holds a BS in Mathematics from the California Institute of Technology.
QUEST 2014 Conference and EXPO Sessions:
During the era in which organizations were evolving their architectures to meet service-oriented standards, the ROI of services was predicated on reuse. The difference between SOA and APIs is the prolific nature in which services, now known as APIs, are being used to extend interconnectivity beyond the corporate boundary. As services cross borders, your APIs and your brand become inextricably intertwined. Thus, while SOA required trust, APIs demand integrity. The more secure, reliable, and dependable your API, the better the chance of consumption and the greater the potential for business expansion. However, if you’re providing a questionable interface, you are likely to lose business since switching costs associated with API integration are so low. This presentation explores the top three challenges to API integrity and outlines strategies and best practices for reducing the risks associated with each challenge. The challenges discussed will include a significantly increased attack surface area, elevated potential for unintentional or malicious misuse, and validating performance in the event of the erratic or surging demand.