Moilanen (PhD, 3D printing ecosystem) Chief Development Officer, Platform of Trust Author of API Economy 101 Business Lead of API management solution (2017) Founder of APIOps (2015) ”Doctor of Developer eXperience” 2nd PhD in process (Data Economy and DX) @Twitter_name Experiences from the field Ewww! In Twitter: @Jarkko_Moilanen
are filled with APIs According to Benzell et al API adoption increases firms' market value by 10.3% Architectural flexibility Expected by the markets Easier use (and replacement) of external services as part of the solution
options to choose from Full Life Cycle API management • Product Management oriented All pretty good – looks shiny. None can deliver excellent solution as is Result: top companies build a puzzle (mix of commercial, open source and in-house)
of the bugs in software come from 20% of the features. • 80% of the complexity in a given application comes from 20% of the code base. • Only 20% of a given feature set in an application is important to 80% of the users. • A given engineering team spends 80% of its time on 20% of the application. You DONT want your API to be involved in the 20% code base You DONT want your API to be involved in the 20% of the features You WANT to enable that 20% of the features You WANT to decrease the time needed with your API Pareto is your friend in finetuning DX and product
API endpoints are mostly used? • What to optimize and focus on + why + find patterns • ”80% of the value comes from 20% of the features.” • You have limited resources – be wise – data driven decisions • What are the common 400s? • Why are users using it wrong? • ”80% of the bugs come from 20% of the code.” • It might not be bug, it is most likely a usability issue (DX) • Is the documentation outdated? Wrong? Missing? • Is some requirement parameter missing? • Which API calls have long time response time? • Why? API management analytics and Pareto
is just a SMALL piece of the puzzle • Feedback management • API Design management • Specification(s) to use • API architectures (REST, GraphQL, realtime) • Mockups for validation • API docs generation • Code libraries • QA / testing • Implementation • Deployment • Marketing This is why providing Full API Life Cycle as a single tool is hard
is just a SMALL piece of the puzzle • Feedback management • API Design management • Specification(s) to use • API architectures (REST, GraphQL, realtime) • Mockups for validation • API docs generation • Code libraries • QA / testing • Implementation • Deployment • Marketing This is why providing Full API Life Cycle as a single tool is hard Product thinking!
design management – use Design Guide – this is the bible! • Practices (naming, error handling, auth…) • Steering the API family (you will be ”mother of a dozen”) • Must provide value, enforce it! • Versioning – deprecation – migration support – product life cycle thinking! • Customer focus • Create guides (in developer portal) • Supports customer paths: New user -> guides -> API documentation • Business models & pricing • Not solved with one tool! It’s a puzzle and about processes Some notes on API Governance