Presentation at API Days Berlin 2014: rulepool an architecture for guidance in the API Economy.

1. rulepool: Architecture for Guidance in the API-Economy
Olaf Resch

2. • Since 2006 Lecturer of
Informationmanagement and E-Business at
Berlin School of Economics and Law
• www.hwr-berlin-de
• Research interests: API-Economy, BRM and
Internetsociety.

4. Application Programmming Interface
URL url = new URL( "http://api.opencalais.com/tag/rs/enrich" );
HttpURLConnection connection = (HttpURLConnection)
url.openConnection();
connection.setRequestProperty( "x-calais-licenseID", apiKey);
connection.setRequestProperty( "Content-Type", "text/raw;
charset=UTF-8" );
…

5. API: data -> functionalities -> competency

7. API-Economy: doing business based on
multilateral, anonymous and dynamic
networking.

8. Dynamic Networking is great
for Business.

9. Turn Offs Buyerside
• Ignorance.
• Inertia.
• Pure Fear.
• Buying because of the nice Salesperson.
!
• ComplexityAVOIDANCE.

10. Turn Offs Sellerside
• Unclear Business Models.
• Coarse grained Product Line.
• Low scalable Pricing.
• Demanding TOS.
!
• ComplexityIGNORANCE.

11. Business Rules:
!
Guide Business Behaviour,
Aligned with Strategy,
Automated with Rule Engine,
Maintained by Domain Expert with Rule
Builder.
!
NEED: Functionality to become active.
!
A Gold Customer always receives a 10% discount

12. API’s:
!
Huge reservoir of functionality.
NEED: Guidance.
!
Thus Made for Each Other☺

13. rulepool project
<Ad>serioussearch.de</Ad>

14. + Business
Technology
+ Business

15. I think….
!
API‘s
+ Culture
+ Complexity Management (e.g.rulepool
= API-Economy.
!
What do you think?

16. Thank you for
your Attention
and be well!