The document discusses the business drivers behind the increasing use of APIs by enterprises. It explains that APIs allow computer systems and applications to connect and integrate both internally within an organization and with external partners. The main business goals driving greater API usage include expanding customer reach through mobile and social channels, integrating internal and external systems like those in the cloud, instrumentation of field devices to gather operational data, generating revenue from API usage, and enabling innovation through access to external developers. Effective API management is needed to ensure APIs meet business goals and address security, access control, analytics and developer support.
On our own we could create an API in 20 minutesPut us together and it would be much more difficult
Head = smaller population, consuming moreTail = larger population, consuming less individuallyGoal is to take advantage of collectiveor to cast the net wide and hope one of the long tails become successful
On our own we could create an API in 20 minutesPut us together and it would be much more difficult
Note these are largely about relationship with client devs
Why are API publishers opening up their APIs? What are their motives? This will help us choose APIs that have reasonable business modelsNeed a better word for integration (trying to describe b2b scenarios driven by the business)
THE IMPORTANCE OF API MANAGEMENT AND SECURITYPurpose: Why now, more than ever, API management & security is of vital importance to the enterprise. Talking Points:The technology that drives much of this activity – sharing to the cloud, sharing within departments, and to mobile – is enabled by APIs. These are a transformative force today. API’s allow virtually anyone to develop and everyone to consume.APIs are no longer just about apps on the internet. They are increasingly the way in which companies exchange data and services, both internally and externally. They are the access point, the connection point, the ‘handshake’ that occurs during a transaction of information.We use APIs all day - any time we use our computer or tablets or phones to ping someone or something for information – the data is shared through an API. Checking transit schedules, Facebook status updates, stock ticker prices, uploading pictures to the web, retrieving data from the cloud, synching our kindle reader page to our kindleTherefore, it’s important to understand the operations of this API ecosystem and identify opportunities within it.Now more than ever, developer communities have a more centralized role because they build the apps that reside on these APIs.It is vital that APIs are scalable, consistent, measurable, and secureThe big question now, of course, is how can we manage all of this activity securely? And by ‘securely’ what sort of unique issues are we facing?Question: do we want to ask: what are the two API architectures? SOAP/REST should be mentioned here. The circle outside the API icon is either going to be REST or SOAP. The discussion needs to find out from them if they use SOAP or REST. This is critical information to collect.Learning Outcomes: What APIs are, what they can allow a company to do, what the risks are if they’re deployed poorly, how a company can benefit from a solid API solution, and this includes ensuring security is front & center.
HOW LAYER 7 ADDRESSES THE SITUATIONPurpose: Introduce who we are. What we do. What motivates us. Why it is important.Talking Points:Founded in 2002, Layer 7’s software suite sets out to create a solution that addresses the enterprise’s need to share and exchange information in a way that balances collaboration and innovation with security. It tries to answer the question – ‘How can we create a sandbox, or a safe arena, that allows for developer innovation and for systems to communicate and exchange information, but with a specific set of rules and guidelines to ensure that all of the activity is monitored and managed appropriately?’ We want to enable this activity, and arbitrate the exchange at the same time. And we want to be able to do this within organizations that have the most stringent security needs out there.Our software addresses a range of API Needs, including:Connects internal partners/divisionsProvides a secure bridge to the cloud & channels for mobileEnables and empowers internal and external developersSolves Big Data problems in the Internet of ThingsLearning Outcomes:Where we see ourselves in this space and why we feel motivated and confident about our ability to influence and assist.
PRODUCE LINE INTRODUCTIONPurpose: Introduce our 3 main products and their functions; how each address a unique need in the market.Talking Points:Our code base allows us to do some pretty great things. Almost too many, in fact. Learning about all of them can feel overwhelming at times. So let’s view it from the perspective that at the end of the day, there are three main products that we sell. And while all of them are somewhat related and ‘share’ some common functions and features, we can roll them up into our Gateway, the API Portal, and the ESM (though we can make up to a dozen unique license configurations with our code base The API Portal is a developer-friendly interface that allows a company to share, promote, and manage API activity. It helps to engage and onboard internal and 3rd party developers. It has a great community page that educates developers with interactive documentation and resources. It ultimately helps to manage and monetize developer activity.The Gateway is the workhorse behind our products that allows companies to write policies and rules that manage and secure all of the traffic and activity that happens – known in the industry as one of the most flexible, adaptable, and comprehensive workhorses in the market today. Within the Gateway we have the Mobile Access Gateway which firewalls mobile apps to maintain security standards in BYOD scenarios, translates comlex on-premise systems into light, mobile-friendly formats, and our SOA Gateway, which centrally manages SOA governance and partner access policies.The ESM is a monitoring and reporting tool that helps companies with complex deployments manage and oversee enterprise-wide activities.Learning Outcomes: That we have a small but robust product line with many features and functions; all essentially roll up into 3 main products that we can position and sell based on client needs analysis.
PRODUCE LINE INTRODUCTIONPurpose: Introduce our 3 main products and their functions; how each address a unique need in the market.Talking Points:Our code base allows us to do some pretty great things. Almost too many, in fact. Learning about all of them can feel overwhelming at times. So let’s view it from the perspective that at the end of the day, there are three main products that we sell. And while all of them are somewhat related and ‘share’ some common functions and features, we can roll them up into our Gateway, the API Portal, and the ESM (though we can make up to a dozen unique license configurations with our code base The API Portal is a developer-friendly interface that allows a company to share, promote, and manage API activity. It helps to engage and onboard internal and 3rd party developers. It has a great community page that educates developers with interactive documentation and resources. It ultimately helps to manage and monetize developer activity.The Gateway is the workhorse behind our products that allows companies to write policies and rules that manage and secure all of the traffic and activity that happens – known in the industry as one of the most flexible, adaptable, and comprehensive workhorses in the market today. Within the Gateway we have the Mobile Access Gateway which firewalls mobile apps to maintain security standards in BYOD scenarios, translates comlex on-premise systems into light, mobile-friendly formats, and our SOA Gateway, which centrally manages SOA governance and partner access policies.The ESM is a monitoring and reporting tool that helps companies with complex deployments manage and oversee enterprise-wide activities.Learning Outcomes: That we have a small but robust product line with many features and functions; all essentially roll up into 3 main products that we can position and sell based on client needs analysis.