The document discusses concepts related to punctuated equilibrium in evolution and business, celestial navigation, and APIs. It notes that while evolution may look gradual in hindsight, it is actually experienced in punctuated bursts of change. Similarly, exploration and business models have undergone sudden shifts that only appear smooth looking back. It emphasizes that to navigate new opportunities, one needs good maps, instruments, and the ability to measure location accurately. The document advocates developing APIs to explore new market niches, and outlines different API strategies like building for first party use, partners, or as a platform. It stresses the importance of defining target market segments, engaging developers, and setting clear industry goals for an API strategy.
We Will Discuss »
- Why APIs are important to your organization?
- Which strategy is right for you: Internal, Partners, Customers or Open API?
- Frameworks and how to map your API strategy to your objectives and target channels
Are you taking advantage of the growing wave of mobile, social and cloud computing? Are you ready for whatever comes next? APIs are one of the most important technologies a business can use to reach new customers, expand partnerships and leverage existing investments in information technology. In this webcast, we'll introduce the core concept of APIs and discuss common patterns of business value.
Designing APIs and Microservices Using Domain-Driven DesignLaunchAny
Presented at GlueCon 2016. Applying good software engineering practices, system design, and domain-driven design for your public APIs and microservices
We Will Discuss »
- Why APIs are important to your organization?
- Which strategy is right for you: Internal, Partners, Customers or Open API?
- Frameworks and how to map your API strategy to your objectives and target channels
Are you taking advantage of the growing wave of mobile, social and cloud computing? Are you ready for whatever comes next? APIs are one of the most important technologies a business can use to reach new customers, expand partnerships and leverage existing investments in information technology. In this webcast, we'll introduce the core concept of APIs and discuss common patterns of business value.
Designing APIs and Microservices Using Domain-Driven DesignLaunchAny
Presented at GlueCon 2016. Applying good software engineering practices, system design, and domain-driven design for your public APIs and microservices
API Product Management - Driving Success through the Value ChainApigee | Google Cloud
We Will Discuss »
- Managing API products to maximize success for direct and indirect users in the value chain
- Planning, building, and evolving an API product at all stages of the product life cycle
- Evaluating and validating your API design and functionality and iterating to build a superior and differentiated product
Learn the basics of building serverless microservices using a combination of AWS and Apigee. We'll go over major components of the emerging serverless stack, including AWS Lambda, AWS DynamoDB, OpenAPI, and Apigee Edge.
Developers are increasingly using Kubernetes to deploy, scale, and manage their containerized applications. So, how can you securely manage and gain visibility for the APIs deployed for these applications?
This webcast will cover:
- how native integration allows app developers to easily manage application endpoints
- how to transparently add security [oauth/key] for your application containers and endpoints
- how to transparently manage traffic and track analytics for endpoints exposed through Kubernetes
Platforms, Cloud-Native Architectures, and APIs: Chicago Adapt or Die KeynoteApigee | Google Cloud
Apigee's Chet Kapoor discusses the power of platforms, network effects, cloud-native architectures, and APIs. He presented this keynote at the Chicago stop of the Adapt or Die World Tour on Nov. 17, 2016.
Microservices Done Right: Key Ingredients for Microservices SuccessApigee | Google Cloud
70% of organizations claim to be using or investigating this new trend because the promise of faster innovation, and the ability to independently develop, deploy, and scale components of large applications is hard to resist.
But, challenges exist—both known and unknown. Watch this webcast to identify key ingredients of microservices success.
Punctuated Equilibrium, Celestial Navigation, and APIsSam Ramji
In evolutionary theory, punctuated equilibrium refers to a period of significant environmental stress resulting in rapid, dramatic changes among species. It is a powerful model for understanding the changes in technology, business models and data over the last few decades - changes that have given rise to the age of APIs. In this talk, we'll look at three key themes in the API economy:
•The Evolution of Business Models: From 1st Party to Partner to Platform
•The Evolution of Architecture: From Mainframe to Mobile
•The Evolution of Data: From Silos to Social
If you are interested in flying to the outer space there are only two options, the US Space Shuttle or the Russian Soyuz, and neither of these are available at a reasonable cost or on a regular basis to the general public. The problem is not the lack of financial resources among today's adventure tourists, nor the demand in the marketplace, but specifically the lack of licensed, low-cost, reliable vehicles. That was the thoughts of Richard Stern when he started working on this idea in 1999. Seventeen years later a friend’s consulting firm provided him with a detailed analysis of his company. A document that contained the strategies SpaceUtopia would have to take in order to successfully overcome the crisis.
Zezan Tam's slides at Mobile Monday. Zezan Tam is a Melbourne based entrepreneur. After leaving his job at Boston Consulting Group, Zezan attended Singularity University in Silicon Valley, which kickstarted his thinking and excitement towards technology and entrepreneurship. He is currently working on a number of businesses in Australia, as well as being Entrepreneur in Residence at the University of Melbourne Accelerator Program. He travelled to Yangon to see the Myanmar entrepreneurship scene, and is interested in investing into talented entrepreneurs operating in a vibrant country poised for an exciting growth period.
API Product Management - Driving Success through the Value ChainApigee | Google Cloud
We Will Discuss »
- Managing API products to maximize success for direct and indirect users in the value chain
- Planning, building, and evolving an API product at all stages of the product life cycle
- Evaluating and validating your API design and functionality and iterating to build a superior and differentiated product
Learn the basics of building serverless microservices using a combination of AWS and Apigee. We'll go over major components of the emerging serverless stack, including AWS Lambda, AWS DynamoDB, OpenAPI, and Apigee Edge.
Developers are increasingly using Kubernetes to deploy, scale, and manage their containerized applications. So, how can you securely manage and gain visibility for the APIs deployed for these applications?
This webcast will cover:
- how native integration allows app developers to easily manage application endpoints
- how to transparently add security [oauth/key] for your application containers and endpoints
- how to transparently manage traffic and track analytics for endpoints exposed through Kubernetes
Platforms, Cloud-Native Architectures, and APIs: Chicago Adapt or Die KeynoteApigee | Google Cloud
Apigee's Chet Kapoor discusses the power of platforms, network effects, cloud-native architectures, and APIs. He presented this keynote at the Chicago stop of the Adapt or Die World Tour on Nov. 17, 2016.
Microservices Done Right: Key Ingredients for Microservices SuccessApigee | Google Cloud
70% of organizations claim to be using or investigating this new trend because the promise of faster innovation, and the ability to independently develop, deploy, and scale components of large applications is hard to resist.
But, challenges exist—both known and unknown. Watch this webcast to identify key ingredients of microservices success.
Punctuated Equilibrium, Celestial Navigation, and APIsSam Ramji
In evolutionary theory, punctuated equilibrium refers to a period of significant environmental stress resulting in rapid, dramatic changes among species. It is a powerful model for understanding the changes in technology, business models and data over the last few decades - changes that have given rise to the age of APIs. In this talk, we'll look at three key themes in the API economy:
•The Evolution of Business Models: From 1st Party to Partner to Platform
•The Evolution of Architecture: From Mainframe to Mobile
•The Evolution of Data: From Silos to Social
If you are interested in flying to the outer space there are only two options, the US Space Shuttle or the Russian Soyuz, and neither of these are available at a reasonable cost or on a regular basis to the general public. The problem is not the lack of financial resources among today's adventure tourists, nor the demand in the marketplace, but specifically the lack of licensed, low-cost, reliable vehicles. That was the thoughts of Richard Stern when he started working on this idea in 1999. Seventeen years later a friend’s consulting firm provided him with a detailed analysis of his company. A document that contained the strategies SpaceUtopia would have to take in order to successfully overcome the crisis.
Zezan Tam's slides at Mobile Monday. Zezan Tam is a Melbourne based entrepreneur. After leaving his job at Boston Consulting Group, Zezan attended Singularity University in Silicon Valley, which kickstarted his thinking and excitement towards technology and entrepreneurship. He is currently working on a number of businesses in Australia, as well as being Entrepreneur in Residence at the University of Melbourne Accelerator Program. He travelled to Yangon to see the Myanmar entrepreneurship scene, and is interested in investing into talented entrepreneurs operating in a vibrant country poised for an exciting growth period.
The most innovative guys in the room don't always winAdam Higdon
The most innovative guys in the room don’t always win – Imitation has been a successful strategy for many leading companies in a variety of industries. Armen Alchian’s 1950 article built off of Adam Smith’s prior notion of the “invisible hand,” when Alchian introduced his evolutionary model of survival that included a firm’s “adaptive behavior,” and the market’s “adoptive forces.”
Datanauts: Open Innovation & Earth Observation (Proposal)Wolfgang Weicht
European Commission's Copernicus program for earth observation is not only about big data, but also about big ideas. TEDxRheinMain's Datanauts initiative is a proven concept dedicated to spark the creation of great ideas. Leveraging visionary thinking, talent and skills using custom-tailored ideation tools. We are looking for visionaries to bring this two opportunities together.
https://www.linkedin.com/company/tedxrheinmain
http://hello.datanauts.org
The Purdue IronHacks are the world's first virtual Open Data Hacks. Read more about our work in turning open data into novel and useful applications for the public!
Similar to Punctuated Equilibrium, Celestial Navigation,and API Strategy (20)
APIs have revolutionized how companies build new marketing channels, access new customers, and create ecosystems. Enabling all this requires the exposure of APIs to a broad range of partners and developers—and potential threats.
Learn more about the latest API security issues.
Magazine Luiza is a top retailer in Brazil that operates 800 stores and nine distribution centers.
It sets itself apart from rivals with its multi-channel sales platform and innovative digital strategies.
Do you want to scale your API program? Do you want to create new business opportunities with developers and partners? If so, monetization might be the right strategy for you.
Monetization is influencing how APIs are delivered. It provides the flexibility to generate different API consumption models for developers, and it opens opportunities to derive value from APIs, for developers and for partners.
Learn about:
- Monetization trends and best practices
- The industries that leverage API monetization today
- The future of monetization
Watch the live demo of Apigee's API platform to learn how to:
- easily configure and manage new APIs and enforce security with minimal impact to backend services
- create, manage and monetize API products
- extend API Services to increase flexibility and tailor to business requirements with JavaScript, Java, Python, and Node.js
- provide developers easy, yet secure access to explore, test, and deploy APIs
- use end-to-end visibility across the digital value chain to monitor, measure, and manage success
Ticketmaster, the leader in ticket sales and distribution, uses APIs to simplify event discovery and partnerships.
APIs and API management are key to the company realizing its mission to “bring moments of joy to fans everywhere.”
AccuWeather: Recasting API Experiences in a Developer-First WorldApigee | Google Cloud
Learn about the strategy behind AccuWeather’s decision to launch a developer portal and the technology and business considerations required to open up its APIs.
App modernization projects are hard. Enterprises are looking to cloud-native platforms like Pivotal Cloud Foundry to run their applications, but they’re worried about the risks inherent to any replatforming effort.
Fortunately, several repeatable patterns of successful incremental migration have emerged.
In this webcast, Google Cloud’s Prithpal Bhogill and Pivotal’s Shaun Anderson will discuss best practices for app modernization and securely and seamlessly routing traffic between legacy stacks and Pivotal Cloud Foundry.
Apigee's Ed Anuff and Bala Kasiviswanathan will discuss how these forces inform and drive the Apigee product roadmap. Join Ed and Bala for a preview of how Apigee will deliver on its product goals, including a common stack that enables us to address our customers' multi-cloud opportunity. Learn how we'll help companies transition to the PaaS/cloud-native future, how we'll leverage Google's OSS presence, and how we will continue to emphasize the needs of developers.
We'll explore how 4 forces will impact the API market over the next two to four years, and how hybrid- and multi-cloud, open source, developer-led adoption, and cloud-native application architecture are driving profound changes in the API market.
With a focus on three core customer strategies: convenience, loyalty, and extraordinary customer and patient care, Walgreens uses Apigee to: connect digital experiences directly to stores; extend its assets into innovative ecosystems and increase the value of its stores; improve the developer experience
Learn how to deploy a lean API runtime infrastructure in your private enterprise environment while getting all the benefits of Apigee Edge API management in the cloud.
Dive into a reference architecture that demonstrates the patterns and practices for securely connecting microservices together using Apigee Edge integration for Pivotal Cloud Foundry.
We will discuss:
- basics for building cloud-native applications as microservices on - Pivotal Cloud Foundry using Spring Boot and Spring Cloud Services
- patterns and practices that are enabling small autonomous microservice teams to provision backing services for their applications
- how to securely expose microservices over HTTP using Apigee Edge for PCF
Watch the webcast here: https://youtu.be/ETT6WP-3me0
Pitney Bowes uses API management to deliver a broad set of cloud-based digital ecommerce capabilities, enable extensive partnerships, and optimize its own operations.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
27. G. Scandens C. Pallidus G. Magnirostris G. Conirostris C. Heliobates G. Fortis G. Fulginosa C. Psittacula C. Pauper C. Olivacea C. Parvulus Certhidea Camarhynchus Geospiza
28. “Thus, from the war of nature, from famine and death, the most exalted object of which we are capable of conceiving, namely the production of higher animals directly follows.” Charles Darwin On Origin of Species
29. So while it may look slow and gradual in hindsight
33. Navigation Navigation While it’s nice to think that evolutionary change happens in a planned way, this is not the case – it only looks smooth in hindsight. Not even the voyage of Darwin’s HMS Beagle was smoothly planned. Looking back he seems to have been predestined to arrive at the Galapagos islands, but this is not the case. Planning is hard enough and at best “no plan survives contact with the enemy” (Patton) – so navigation becomes a crucial skill. Knowing where you mean to go is one thing. Knowing where you are and how to move forward is quite another. Realizing that you may in fact be making progress towards a different and better goal, rather than failing to meet your original goal, can be the key to success. Columbus may have set out to find India but as a result Spain fared extremely well through the discovery of the Americas. Dead reckoning – the art of knowing where you are based observing your speed and direction over time. Very difficult and subject to cascading error. “coasting” like the ancient Greeks Word of mouth and story-based navigation “books” - portolani Blue-water sailing – takes instruments, maps, goals. Necessary when there are no landmarks in sight. Shaping of the hull, multiple masts, the rudder – enabling the ship to sail closer to the wind and cross the oceans. (AKA Technology). But this was not enough – a way to manage this was needed in order to achieve the goal: compass and sea-chart navigation. Pole Star – Stella Maris Astrolabe Columbus – set out to make landfall at 24 degrees north and succeeded, although in America and not China Started with a map like p18 and p20, but we’ll give you one like p35 or p52 Sea charts transformed the world view APIs Are a bit like sailing off to find new lands and opportunity. But while the first to travel may have had to suffer through early tools, poor maps, and hostile natives, you can learn from their experience, borrow their maps and the tools they had to invent to succeed. Military advantage came from percentage-point improvements in navigational accuracy – and time became a military technology. The more precisely you could measure time itself – and keep the measuring devices in sync across your fleet – the more effectively you could compete and win.
101. App Developer Device App Big Box Retailer Mobile App National Chain Web Retail Department Store Web Catalog Specialty Store Indirect Sales Direct Sales
103. Hardt’s Theorem: The Internet Power Law The first wave of the Internet demonstrated the economic impact of web-based business models. 99:1 95:5 The API-driven Internet is demonstrating the next concentration of power and is reflecting a “99:1” distribution (examples: Twitter, Facebook) due to the high switching costs and effective lock-in through software. The HTML-driven Internet showed new business models that focused revenue in the 3rd standard deviation (examples: Amazon, EBay). Reality reflected a “95:5” rule where 5% of companies dominated the transactions and profits. 80:20 Previous eras of business showed a normal distribution for revenue, with most firms getting most of the revenue. In the later half of the 20th century, business model innovations focused revenue in the 2nd standard deviation above the mean. The “80:20” rule became conventional wisdom. The next wave of the Internet is demonstrating the economic impact of API-based business models.
104. But you need to tackle it in a way that fits your business
180. Controller Model View iPhone Wrapper Recommendations R12n Service Xbox Wrapper UNIFIED LIST/TITLE API Wii Wrapper User Info User Service PS3 Wrapper Similar Movies Similar Movie Service SHARED API INTERFACES Roku Wrapper Movie Metadata DataNormalization & Resiliency iPad Wrapper USER API Viewing History Apple TV Wrapper Ratings PC / Mac Wrapper TiVo Wrapper API Repository Layer Wrapper Layer Web Service Layer Shared Layer Source Data Layer App Layer API Layer
181. Stable Flexible Agile iPhone Wrapper Recommendations R12n Service Xbox Wrapper UNIFIED LIST/TITLE API Wii Wrapper User Info User Service PS3 Wrapper Similar Movies Similar Movie Service SHARED API INTERFACES Roku Wrapper Movie Metadata DataNormalization & Resiliency iPad Wrapper USER API Viewing History Apple TV Wrapper Ratings PC / Mac Wrapper TiVo Wrapper API Repository Layer Wrapper Layer Web Service Layer Shared Layer Source Data Layer App Layer API Layer
183. Instance Architecture Based on Specialization List Creation Dependency Service ELASTIC INSTANCE LAYER API METADATA CACHING LAYER Meta Data Dependency Service METADATA SERVICE
184. Instance Architecture Based on Specialization Handles Request/Response List Creation Dependency Service ELASTIC INSTANCE LAYER Caches Dependency Data API METADATA CACHING LAYER Meta Data Dependency Service Populates and Manages Cache METADATA SERVICE
185. Map out your usage patterns and cache your data accordingly
199. Extend your API by extending data types Addition is not version-worthy Better to be incomplete than inaccurate Withhold implementation if you are unsure
200. Don’t forget to support your API With technology, people and management
203. Service Level Agreements (SLA) Set reasonable SLAs Will vary based on API Communicate them to customers Set up monitors Monitor average latencies at various percentiles Monitor error rates and types Trigger alerts when SLAs get broken Establish escalation and response policies Who responds? What is the escalation plan?
204.
205. Use metrics to guide your decisions They provide better navigation than anything else
206. Metrics / Business Intelligence Request-Based Metrics (default) What endpoints were called? What parameters were passed in? Response-Based Metrics What was delivered? If applicable, what was presented? Was the response valid? Request Trace What underlying systems were called? How did they respond? System Health Are the systems meeting uptime SLAs? Are they performing with reasonable latencies?
207. Metrics (continued) They can affect the future design of the API They can inform strategic business decisions They can reveal rogue usage They can reveal errors in the system
209. DataFrom Silos to Social Silos Better than a random collection of flat files! At least it’s all in one place! Shared (in the enterprise) History: Data warehousing and insights (extra-enterprise) Now: OData shared with communities according to business model Pubsub - Events & Async – better for the provider, better for the app Relevance/Collaborative Filtering/Community Modeling From aggregating data or mixing data to produce a contextual recommendation or view Domain-specific database monopolies Social Bootstrapping social context within your own data via the Facebook Graph Surround your customer by understanding their context and delight them Understand Domain-specific database monopolies – location, messaging, more Look for experts in other domains that you need Is the verb “enrich” instead of deliver? From content to experiences
210. Domain-specific Data APIs Private Cloud DBs Caching DBs Data API Data Warehousing Mainframe RDBMS Flat file Shared Silos Data
215. optimize data delivery enable larger downloads for fewer queries more liberal retention policies fewer refreshes, less breakage push incremental updates limited access to richer queries
216.
217.
218. Highest rated titles from the 80's and their awards: http://odata.netflix.com/Catalog/Titles?$filter=ReleaseYear le 1989 and ReleaseYear ge 1980 and AverageRating gt 4&$expand=Awards
219. [{ "id": null, "name": null, "type": "/dining/restaurant", "/business/business_location/address": [{ "street_address": [], "citytown": { "id": "/en/toronto" } }], "cuisine": [{ "/dining/cuisine/region_of_origin": [{ "!/film/film/featured_film_locations": [{ "id": "/en/the_italian_job" }] }] Find Toronto restaurants with cuisine from a filming location of "The Italian Job"
225. Open your database via an API and let others access + download RPC-like access to a database is not a great idea SQL-like access makes more sense – which indicates OData (but beware being tied to a Microsoft infrastructure)
232. Private, partner vs. public API audience continuum Start with partner - minimize work partner needs to do - security IT->Strategic Partners->Platform Modular vs. one-off, scenario APIs What API team can do vs. what others can do Diversity of implementation can have costs Mainframe to modern internet evolution Internet vs. API-enabled Internet (HTML 5 + AJAX + API) - Efficiency in development (well defined model) - Best UI experience - Why is this better than an IFRAME - IFRAME on top of API - Optimize once scenario and UI platform considerations are well understood Platform angle can create big opps for businesses, but you have to commit. Big resource commitment.
http://upload.wikimedia.org/wikipedia/commons/thumb/6/69/Punctuated-equilibrium.svg/1000px-Punctuated-equilibrium.svg.pnghttp://www.talkorigins.org/faqs/punc-eq.htmlThere are two models for the flow of evolution, each with its adherents. Phyletic gradualism says that things change slowly over time, day by day, until one day you realize there has been enough change that something new has arisen.The opposing model is Punctuated Equilibrium. This model says that species tend to remain in a homeostatic mode of stable equilibrium – but that every so often some significant new stress affects the environment, prompting rapid, dramatic changes that settle down into equilibrium again.For our purposes, punctuated equilibrium serves as a powerful model for viewing the changes in technology, business models, and data over the last few decades and shows us that the rapid, dramatic changes part of the cycle is coming again.
http://www.csuchico.edu/~curbanowicz/DarwinSP2002Phil108.htm"Thus, from the war of nature, from famine and death, the most exalted object of which we are capable of conceiving, namely the production of higher animals directly follows. There is a grandeur in this view of life, with its several powers, having been originally breathed by the Creator into a few forms or into one; and that, whilst this planet has gone cycling on according to the fixed law of gravity, from so simple a beginning endless forms most beautiful and most wonderful have been, and are being, evolved
Cherokee-class 10-gun brig-sloop of the Royal Navy downgraded to a 6-gun barquehttp://www.theora.com/msdb.php/OriginOfSpecies/orderBy/subject/msdbCat/subject/12%20-%20Geographical%20Distribution%20--%20continuedExploration - like evolutionary change - only looks smooth in hindsight. Not even the voyage of Darwin’s HMS Beagle was smoothly planned. Looking back he seems to have been predestined to arrive at the Galapagos islands, but this is not the case.
http://darwin-online.org.uk/people/chancellor.htmlAt some points the trip got pretty rough.
http://thebeagleproject.blogspot.com/2008_07_01_archive.htmlAnd the voyage itself was anything but linear.
http://www.csuchico.edu/~curbanowicz/DarwinSP2002Phil108.htm"Thus, from the war of nature, from famine and death, the most exalted object of which we are capable of conceiving, namely the production of higher animals directly follows. There is a grandeur in this view of life, with its several powers, having been originally breathed by the Creator into a few forms or into one; and that, whilst this planet has gone cycling on according to the fixed law of gravity, from so simple a beginning endless forms most beautiful and most wonderful have been, and are being, evolved
Credit to Dick Hardt who formulated this in December 2010.
http://www.csuchico.edu/~curbanowicz/DarwinSP2002Phil108.htm"Thus, from the war of nature, from famine and death, the most exalted object of which we are capable of conceiving, namely the production of higher animals directly follows. There is a grandeur in this view of life, with its several powers, having been originally breathed by the Creator into a few forms or into one; and that, whilst this planet has gone cycling on according to the fixed law of gravity, from so simple a beginning endless forms most beautiful and most wonderful have been, and are being, evolved
Also in 2010, Twitter announced at Chrip Conference that 75% of its total traffic comes from sources other than Twitter.com. This is part of a growing trend where new, emerging companies gain relevance on mobile and connected platforms other than the web.
The Netflix API is a good example of how metrics can influence the design of the API.As Mike talked about earlier, the Netflix API was originally launched to let 1000 flowers bloom.Over time, we started adding our own devices to run off the API.
Also in 2010, Twitter announced at Chrip Conference that 75% of its total traffic comes from sources other than Twitter.com. This is part of a growing trend where new, emerging companies gain relevance on mobile and connected platforms other than the web.
The Netflix API is a good example of how metrics can influence the design of the API.As Mike talked about earlier, the Netflix API was originally launched to let 1000 flowers bloom.Over time, we started adding our own devices to run off the API.
As a result, we are in the process now of redesigning the API with an emphasis towards supporting our devices, while trickling down API features to the 1000 flowers.
Another key metric going into our redesign is total requests per month. The growth of the API skyrocketed around October/November. Scale is one of our biggest issues moving forward and continuing on this trajectory will create more challenges.
REST is dominating APIs – expanding share of APIs even as the number of APIs is exploding (from just over 1000 in 2008 to over 3000 in 2010).
Netflix: Groups of entire movies will be stored together
Netflix: The same part of all movies will be stored together – such as frequently-used data about the movies such as actors, director, synopsis, first few minutes of video, etc.
Netflix: The same part of groups of movies will be stored together
And don’t just design the API based on your current audience. Dream big and design the system for the audience that you want. That doesn’t mean you need to implement the system for the dream audience. It just means your designs should allow for the system to scale to that audience.
Similar to the rapid changes we've seen in API-enabled business models and related architectures, we've witnessed four major shifts in how data is shared.Back in the mainframe days that Daniel spoke of, flat file data storage ruled and data sharing was fairly non-existent. Allowing multiple applications to access the same file was impractical.Databases with concurrency controls through locks made sharing more possible, as you could now more easily let multiple apps manipulate the same data. However, having applications work directly against data in the format with which it is stored introduced a very tight dependency that could be hard to manage.Middleware introduced another layer that allowed applications to share data via messages to applications, insulating the apps from the actual storage format of the data, effectively making those apps immune to changes in data storage format and schema.Web services improved data sharing even further. The adoption of the internet-friendly HTTP protocol for exposing data now lets sharing occur beyond the boundaries of your business, while also lowering the technical expertise and software required for consumers of the data.
So technology has evolved to enable unprecedented levels of data sharing. How can a business successfully navigate the opportunities and threats of this new world?[Honestly assess the cost, benefits and risks of sharing your data]Sharing your data via an API entails a different set of considerations than other forms of APIs. Why?You lose significant control once data passes out of your API- Unlike non-data APIs, you can't technically restrict access to data once it's been retrieved, although you can restrict access to data in the future- At that point left mostly with legal recourse as defined by any restrictions in your TOU, which is a very blunt enforcement instrument- Enforcement of TOU can be expensive, in terms of your time, money, and reputation with developers, esp. if you seek legal recourse (even if you're right)That being said, it may be time to get over your control issues- Be honest about the value you might get from sharing your data as well as the costs and risks of sharing it
Case study: opening up Netflix movie metadata- Value of sharing: others build great movie discovery experiences -> enables Netflix as a fulfillment option- Costs: - on par with anyother API for allbut - Risk: competitor uses the data to bootstrap their business - data islargely public domain or otherwisereproducible with a small to moderate degree of effort - with controls: can easilycut off a developer'saccess to new data, whichisfairlycritical - TOU - enforcelimits and dev account revocation - nuclear option: legalrecourseCounter example: Hoovers, which has contact information for executives of top companies, their data is their asset
[Optimize your data delivery strategies]1. Consider allowing the download of larger datasets, providing an efficient way to get updates, and allowing liberal retention policies to improve availability, scalability and query-ability- Only allowing bite-sized data requests will cause developers to make many more queries which will affect your scalability- Retention restrictions, such as a one-day limit on data retention, will encourage developers to come back often to refresh their data- even if the data hasn't changed- Both result in higher scalability requirements for your API, which costs money- More frequent requests means an increase likelihood you'll break an app dependent on your data, assuming your service is anything less than 100% available- Push or publish incremental updates to consumers so they don't have to download the world regularly2. Consider limited access to richer queries to determine what new APIs to provide
Basics:[Netflix service screen shots? Create two slides if so]- Lists (a user's queue, recommendations, watching histories)- Text search on entity names (Movie titles, actor names, etc.)- Not super-flexible, but how customers use the business. Limits innovation space.[Netflix movie title API output?]Inevitably, esp. for larger and more interesting data sets, developers will want to slice-and-dice the data- creating queries combining data fields to get very specific subsets of large data sets- minimizing data returned in results to optimize performance- writing a query engine is probably not your core competency, but there are a few options available, albeit with some limitations
Two emerging web-based query engines can provide rich query semantics for your data without requiring you to make large data sets available for downloadAPI limits can be tough with open query access. Consider limiting access (OData) or offloading the work (Freebase).Caveat structor: We haven't seen anyone solve this problem at massive scale, however.Once you use platforms like OData or Freebase and find successful and/or common access patterns to your data, make it a new data API.
Open standard, backed by MS under their Open Specification PromiseThe describe it as “a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today”They provide implementation help for enabling OData on your API servers. .NET producer libraries most mature, other libraries (e.g. Java) starting to emergeIn simpler terms, it enables rich query semantics for your data APIHighest rated titles from the 80's and their awards:http://odata.netflix.com/Catalog/Titles?$filter=ReleaseYear le 1989 and ReleaseYear ge 1980 and AverageRating gt 4&$expand=Awards [json]
Wikipedia of structured dataYou push your data into their serviceVery robust query language and APICan query across your data as well as other sources of data with common entities (e.g. an actor, a screenplay, etc.) - Example: Actors that have co-starred in a movie with Kevin Bacon that have also been in a movie with a screenplay adapted from a Steven King novelLicensing of hosted data is creative commonsFreebase is in control of the data, their rules, limits, availability, etc.
API limits can be tough with open query access. Consider limiting access (OData) or offloading the work (Freebase).Caveat structor: We haven't seen anyone solve this problem at massive scale, however.Once you use platforms like OData or Freebase and find successful and/or common access patterns to your data, make it a new data API.
While most of our API discussion today has focused on how to open up your business to others, we'd be remiss if we didn't call attention to the value that can be attained by pulling data from other API providers into your business. Think about whether it would be valuable for your business to understand:
1. Would it be useful for your business to know which of your customers are friends? Facebook friends[clipart of friends]What does that logo mean to you today? Maybe it's time to think about it differently.
2. What businesses do your customers frequent? Foursquare and Facebook check-ins[clipart:high scale shop vs. low-rent shop]
3. What is the gender or age of your customers? Facebook core profile [clipart: old man and young girl]The next wave of data competition is not only about what data you can provide, but what outside data can you integration into your business?