Posted on by SATURN Conferencein
Notes by Scott Shipp
Past, Present, and Future of APIs for Mobile and Web Apps
Ole Lensmar, SmartBear Software
Ole Lensmar is from Sweden and has been in the API space since the late '90s. He has created one of the most popular API testing tools in the world SoapAPI. He also is the CTO of SmartBear solutions.
Once upon a time, people tried to connect distributed systems with
They all had their challenges. They were complex, proprietary, limited, etc. To get the scale you wanted, it was very difficult.
Then... ... the internet came along.
They realized it wasn't just for hypertext but could be used to connect distributed systems together.
Examples: HTTP, XML, POX, HTTP+XML, SOAP (Microsoft).
SOAP tried to take the notion of RPC further and provide a messaging infrastructure that did not necessarily bind you to HTTP.
Next...REST (2000). Thesis from Roy Fielding in 2000. REST is now by far the most popular way to build web APIs, but took a long time to take off.
SOAP 1.1 (2003) Everyone did SOAP their own way.
WS-I Basic Profile (2004) Created a rule-set for how to apply SOAP standards. People who do SOAP today adhere to this in order to prevent "everyone doing SOAP their own way." Doc/Literal replaces RPC. Simultaneously people were talking about a top-down (design APIs first) vs. bottom-up design.
Web APIs Emerge
Also...Web applications became much more dynamic.
...web starts turning into a platform.
SOAP became "enterprisy"
(That being said, SOAP is still huge in the enterprise. SOAP users are still growing every day.)
SOA architectures became "mainstream." Public APIs did not utilize SOAP. Very difficult to apply SOAP to that space.
The client landscape continues to evolve as well.
APIs fuel cloud and infrastructure.
APIs are at the heart of applications. Provide basis for composite architectures.
APIs just continue to grow.
Question: will proliferation of QoS standards kill REST as�it did for SOAP?
API growth recap Slides - diagrams of example enterprise architectures shown from 10 years ago until now. From monolithic to distributed.
"API-Oriented Architecture" What Ole calls this:�Picking components (APIs) off the shelf as the key ingredients in a distributed application architecture.
What is REST? Not a technology. An architectural style. (SOAP is not an arch style...it is a technology).
Components of REST
Pros: Allows server to change URIs if it needs to. Cons: Human concept. Someone must read this and adapt to the changing list of resources.
Examples provided for HATEOAS RES requests and responses.
REST API descriptions
LOOKING AHEAD---REST CHALLENGES:
Parting thought: Love your APIs and they will love you back.
Presentation link: http://resources.sei.cmu.edu/asset_files/Presentation/2014_017_101_89993.pdf
Making a Language Switch at Google Patrick Riley, GooglePatrick Riley has led Google's efforts around search logs. Made significant changes to log contents and way the data is analyzed. They record each searche's query, timestamp, user-agent, etc. Then they collect them all together. Logs are used for "Google Zeitgeist," identifying Chrome vs. IE user-base behaviors (quantitatively) In other words: Search logs very useful for providing good things to users. Google has a core infrastructure for log processing. Two groups use it: 1. content experts / library maintainers 2. Engineers and analysts who write small bits of code to get interesting things from the logs. SAWZALL
Why switch from Sawzall now?
....this talk focuses on how Google went through the decision-making process. Needed everyone at Google to buy in and contribute to the change. First, identified stakeholders (and concerns). Second, found partnerships. Partnership between team lead of infrastructure team and Patrick Riley with foot in camp of engineers/analysts and camp of log content experts. Third, identify possibilities that are better than Sawzall.
Fourth, Created a summary doc.
Fifth, Based on summary doc, wrote a small (two page) decision doc.
Sixth, a series of steps. Reflecting--was it the right choice?
Morals of the story: