Smartone v1.0
•Download as PPTX, PDF•
0 likes•716 views
Apigee Edge is a platform for API management that allows organizations to securely publish, monitor, and manage APIs. It provides API services including security, traffic management, analytics, and developer services. Apigee Edge handles the full lifecycle of APIs from development to publishing to consumption. It offers capabilities for access control, analytics, monitoring, documentation and more to help organizations maximize the value of their APIs.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Smartone v1.0
Similar to Smartone v1.0 (20)
Recently uploaded
Recently uploaded (20)
Smartone v1.0
- 3. How many API calls do you make in a single day?
- 4. APIs Power Our Daily Lives 4 Music Streaming Television Programming Online Shopping Navigation Banking Stock Quotes Telecom Services Mobile Phone Provisioning Photo Printing Social Networking Video Conferencing Web Meetings Online Gaming Customer Support Payments In-Store Kiosks Wifi Services Prescriptions Photo Sharing Fitness Tracking Events Ticketing Grocery Shopping Auctions News Books & Magazines
- 5. Each era delivers new innovation-based benefits 5 1960’s, 70’s 1970’s, 80’s 1990’s 2010’s Web, SOAClient Server IoT, APIsMainframe
- 7. Two Speed IT rationalizes two IT realities 7 Intelligent API Platform InsightsConsumer Apps Employee AppsPartner Apps Systems of Engagement Pace of change App Server ESB / Integration / MOM BI CRM ER P Database Data Warehouse Data Lake Systems of Record
- 9. Edge across the value chain 9 ExposureConsumption
- 10. Apigee Edge: Focus on the Complete API Lifecycle 10 Threat Protection Test Monetize Scale Traffic Maintain Availability Update / Iterate Publish APIs Analyze Develop Deploy Model Access Control Data Access Real Time Monitoring Document Use Run Build Apigee Edge Swagger Node.js Design Package Integration Configuration Coding TransformationQuota Monitoring Versions Logging Alerts Debugging Auditing Load TestingStaging DDoS Identity Roles Portal Developers App Registration Rate Plans Documentation Mobile Data Activity Metrics Push Notification Zero Downtime Low Latency Geo-Distribution Traffic Spikes
- 11. API Services
- 12. Edge API Services 12 BackendApps API Management BaaSSecurity API Programmability API Services The best of Internet and enterprise technologies with rock-solid reliability, Internet scalability, and enterprise-grade flexibility
- 13. Manage APIs through Configuration & Programming >30 out of the box policies Policies can be attached at different points and levels Delivering where developers are Manage interactions with API consumers and optimize performance Secure APIs and protect back-end systems from attack Transform, translate and reformat data for easy consumption Extend with programming when you need it 13
- 14. The power of policies Manage interactions with API consumers and optimize performance Secure APIs and protect back-end systems from attack Transform, translate and reformat data for easy consumption Extend with programming when you need it 14
- 15. Programming flexibility to adapt 15
- 16. The “processing pipeline” is powerful and flexible 16 App Backend API Services • Enforce security • Validate request • Transform parameters and payload • Translate between developer- friendly APIs and back-end systems • Build orchestration and optimization via node.js 16
- 17. API Proxies and Flows http://apigee.com/docs/gateway-services/content/flow-configurations 17
- 18. Policies get attached to flows 18
- 19. End-to-end API Trace with replay simplifies debugging 19
- 20. Governance – Hierarchy of Resources 20 Environment Environment Management Server Organization Environment • Users, Developers, Roles • API products • Applications and API keys • Analytics • Granular RBAC for Governance and development life cycle • Resources (cache, …) • Client endpoint configurations • Target endpoints configurations • Centralized control • Each API team (based on their role) can login to Management server and perform variety of tasks: • Create APIs • Create API Products with different access levels • Collect and use the Analytics for their KPIs and SLAs • Manage local governance • Manage the development life cycle Developer Services Apigee Instance
- 21. Demo: API Services – Creating an API Proxy
- 22. 1. Look up weather using city name - http://weather.yahooapis.com/forecastrss?q=hong kong 2. XML to JSON 3. Response Caching 4. Trace – debug API calls 5. Throttle API Traffic using Spike Arrest policy What shall we build? 22
- 23. 23 Start Finish Shopper gets online store ad in email Browses at shoe rack on the website Adds it to his wish list on the website Later he’s close to one of their stores Gets a push notification that the shoe rack is in stock And if he places his order now, he gets a discount He places the order. Chooses in store pickup. Picks up the item in store bypassing checkout. He receives a survey about the item. He fills out the survey. His feedback is posted. A digital use case
- 24. Build Powerful, Modern Applications! APIServices A/B testing Errors & Crashes API Performance Device Analytics Custom Events Session Analytics Datastore Location queries Configuratio n Management Push Notifications Connections/So cial User Management Partner Services BaaS API MRP CRM ERP HR 24
- 27. 27 Graph Data Persistence: Entities & Connections
- 28. 28 API Driven Data Access with Query
- 29. 29 Users, Roles & Security made easy!
- 31. Demo: API BaaS – Location Query
- 35. 35 Remote Application & SDK Configuration
- 36. 36 Beta & A/B Testing
- 37. Demo: API BaaS - Building Social Mobile Apps
- 39. Edge Developer Services 39 API TeamDeveloper Developer Portal Modeling & Management SmartDocs & API Sandbox Monetization Developer Services Backend API Management BaaSSecurity API Programmability API Services Apps Enable a great developer experience that accelerates API adoption, simplifies learning, and increases business value
- 40. API TeamApp Developer Business User Goals and Challenges • How to create a developer portal that is useful and informative ? • What steps to take to make it easy for developers to take the APIs for a spin ? • How to easily publish fresh content for developers and promote events ? • What tools are available to developers to engage with the API team efficiently ? Build, enable and engage your developer community • How to enable new or extend existing revenue streams with APIs ? • What kind of revenue models can I implement ? • How can I make it easy for developers to understand the models & consume them • Is it easy to integrate the data back to my existing financial systems ? Deploy business models for API Products Goal s Challenges • Is it easy to learn and use the APIs ? • How to understand better about the app performance on the device? • Can I view data to easily on my API performance ? • Can I contribute and engage with other developers easily ? Build apps easily, analyze data and engage with other developers 40
- 41. Digital Products out of APIs 41
- 42. Self-service On-boarding 42 Developer signs up and requests key Key approval designation Manage key requests Add App Developer ready to go 42
- 43. Equip developers better API Modeling Describe an API structure SmartDocs Generate interactive documentation API-based Integrate with any portal / CMS Apigee Edge Developer Services gh- pages Other CMS 43
- 44. Build great developer experiences!44
- 45. Easy to Understand Traditional Documentation Interactive Documentation
- 46. Easy to Try Things Out Explanation of How things work Rapid Experimentation
- 47. East to Consume Traditional Web Services “REST” API
- 49. Edge Analytics Services 53 API TeamDeveloper Developer Portal Modeling & Management API Console Monetization Developer Services Backend API Management BaaSSecurity API Programmability API Services Apps Ops Metrics App Performance Developer Metrics Business Metrics Analytics Services Business User Visibility across the digital value chain necessary to monitor, measure, and manage success
- 50. Relevant, Actionable and Extensible Dashboards, Tools & Custom Reports API AnalyticsDeveloper Analytics App AnalyticsUser Backend • API Traffic Patterns • API Performance • Geo location • Anomalies • Multiple metrics – traffic, response times, errors, data exchange, etc. • Top Developers • Developer Engagement • Top API Users • Top Products • Top Apps • App Performance • App Usage • API Performance • Filter by app version, device, platform, OS, etc. End-to-end visibility 54
- 51. Measuring progress and results 55 Product Manager How is API adoption? How can we improve? What is the business impact? Business owner What is the bottom line impact? How do we invest for best return? Ops What is the response time per request? Do I need to allocate more resources at peak times? App Developer How are the APIs my app uses performing? How is my app adhering to API terms of use?
- 52. Custom example: Request data used for analysis Rich, flexible analytics services 56 API Program Proxy Performance Latency Analysis Partner Enablement Business Transactions Custom Reports Top Performance Cache Performance Error Analysis Traffic Composition Geo Map Devices Dashboards: Request payload data Developer and App data Custom metrics Reports and Dashboards
- 53. Get started with built-in reports 57
- 54. Custom reports can show a number of different measures and provide details based on a variety of different drilldown criteria Define custom metrics and dimensions using virtually any attribute that defines traffic Unmatched Customization & Flexibility 58
- 57. Apigee Edge BackendApps API Services API Team Developer Developer Services Monitor, manage, and measure success Analytics Services Business User Increase adoption and value of APIs Build, manage, scale, and secure APIs and Apps Enables digital business acceleration with a unified and complete platform built from the ground up for the digital economy API Management BaaSSecurity API Programmability API Services Developer Portal Modeling & Management API Console Monetization Developer Services Developer Metrics Ops Metrics App Performance Business Metrics Analytics Services 61
- 58. Thank you
- 60. 64 Infrastructure and Compliance Security Framework for Edge Authentication and Authorization • Client-side security features such as OAuth • Integration with custom identity providers • Target-side security Traffic Management • Spike Arrest • Threat Protection • IP address based access control User Management • Roles and Permissions • Request audit log • Pluggable authentication • Cloud or on-premise implementation • Customizable SSL support • PCI / HIPAA / SOC 2 • 24 x 7 x 365 Enterprise Support • Fault Isolation 64
- 61. 65 Apigee Edge API Platform Security Checklist Identity User provisioning RBAC management Groups Identity provider API Security API to Backend (Exposure) Secure communication (TLS – 1 way or 2 way) Authentication (TLS, OAuth, SAML) API Products with permissions Versioning Integration with Enterprise identity providers Logging and auditing App to API (Consumption) Secure communication (TLS – 1 way or 2 way) – Mobile Vs Partner Authentication (OAuth) API key with Product Scope Roles with Developer Keys (permission management) Quota Enforcement Logging policies and auditing Threat Protection XML/JSON Poisoning/Injection SQL Injection DDoS/App-DoS Attacks Quota/Spike Arrest IP based access restrictions Infrastructure Security and Compliance Cloud or on-premise Cloud-based security (AWS/other) SOC 2, PCI-DSS, HIPAA 24 x 7 x enterprise support Analytics Run time detection reports (Volume based, Traffic properties)
Editor's Notes
- How many users? How many devices? How many apps? How many APIs?
- Main Points: The benefits of each tech era require change. Sequential Story: This is not something new. IT has needed new systems to deliver new innovation before. What is (D) or What will be (U): U Analytical or Emotional connection: A Script: Each new enterprise IT technology era succeeds because it delivers new innovation-based benefits. Benefits that outweigh the challenges of adopting it. Benefits that open up new opportunity for business. As you can see, the use of a new approach to IT is not new. This has occurred many times before, the last big era with the emergence and adoption of services-oriented architecture. It provided a new way to facilitate reuse by taking a modular service based approach to application functionality. However along with the design architecture it enabled, it required new components like an enterprise service bus (ESB) and governance solutions No one ever said, “hey I like what SOA can deliver but I think I will do it with my existing client server solution” as it required an ESB and a new approach. As revolutionary as that was at the time, in the 1990s, it was all designed without any knowledge or planning for the mobile revolution that began in 2007 with the iPhone. The same holds true today, a new approach is needed.
- Main Points: The world of the customer has changed with device choice Sequential Story: Adding to the challenge is a device explosion What is (D) or What will be (U): D Analytical or Emotional connection: A Script: There is more to this challenge though that relates to how customers, prospects, or partners consume app functionality. In this new world there is an explosion of device choice. Now need to support an ever expanding list of devices and support them quickly in a meaningful way
- Context for [24]7: What was the “customer-stated” business pain/problems/s the company is trying to solve? The SHARK was hired on to build a platform that would provide their developers the ability to access, and combine the siloed services that will give them a competitive edge. In the current state, they are spending too much time and resources to customize solutions for key customers and are in a constant state of fire drills. With an adaptive API platform, the have the ability to enforce standards in API, app, and data exposure and consumption that will shorten/optimize any customization required. With key customers requiring consumable REST APIs, they need the ability to authenticate and manage those customer APIs as well. What will Apigee enable them to do as a business? Apigee Edge will provide the programmatic layer that will enable them to standardize internal development as well as securely expose their “packaged” services for customer consumption. Role-based analytics will enable the business to understand, strategize, and adapt based on customer requirements and their own advanced customer engagement services. Main Points: Two-speed IT enables greater IT innovation Sequential Story: Now provide the solution What is (D) or What will be (U): U Analytical or Emotional connection: A Script: A new way of addressing the challenges inherent in the digital value chain is to adopt what is called Two Speed IT. You may also have heard of it called Bimodal IT. It Is a concept that acknowledges that both digital and day-to-day IT needs to occur simultaneously. One part works with SYSTEMS OF RECORD—the enterprise resource planning, or ERP, systems companies rely on to run their business (e.g. Financials, manufacturing, customer relationship management, human resources). <CLICK> The SYSTEMS OF ENGAGEMENT LAYER is the customer experience layer—It is used by customers, partners, employees and other users to engage with the business across multiple channels and locations. Systems of engagement are usually more decentralized and incorporate technologies that enable interactions, and they must be faster and more agile than the systems of record to keep pace with dynamic and diverse customer expectations. <CLICK> This also acknowledges that the pace of change is faster with systems of engagement. <CLICK> To achieve the benefits this offers, a new API-centric adaptive layer is required to enable agile and web-scale innovation so that IT can meet evolving business requirements, while allowing existing IT systems to continue to run reliably and securely. Background Info Systems of engagement, which are used by customers, partners, and employees to connect with the business, represent a new focus on communication and collaboration with these constituents for the enterprise. Unlike systems of record—the ERP-type systems that companies rely on to run their business (financials, manufacturing, CRM, HR)—systems of engagement are decentralized and incorporate technologies that enable interaction. Driven by new customer expectations born of the rapid growth in mobile, big data, and cloud technologies, these new systems of engagement harness mobile, social, cloud, and big data innovation to deliver apps and smart products for customers, partners, and employees. To keep pace with dynamic customer expectations and an increasing amount of data generated by interactions and transactions in emerging digital business ecosystems, the systems of engagement must be faster and more agile than the systems of record. It’s all but impossible for many businesses to serve the needs of the systems of engagement; traditional software stacks simply aren’t designed to connect to the rapidly evolving digital economy. Systems of Engagement and The Future of Enterprise IT - A Sea Change in Enterprise IT Written by Geoffrey Moore, Managing Director, TCG Advisors http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CDoQFjAC&url=http%3A%2F%2Fwww.aiim.org%2F~%2Fmedia%2FFiles%2FAIIM%2520White%2520Papers%2FSystems-of-Engagement-Future-of-Enterprise-IT.ashx&ei=EeS7VInrKIORyASw4IDwDA&usg=AFQjCNHch_4MsEstmNQUDWIicmOeQjXUMw&bvm=bv.83829542,d.aWw Systems of Engagement and The Future of Enterprise IT A Sea Change in Enterprise IT Over the past decade, there has been a fundamental change in the axis of IT innovation. In prior decades, new systems were introduced at the very high end of the economic spectrum, typically within large public agencies and Fortune 500 companies. Over time these systems trickled down to smaller businesses, and then to home office applications, and finally to consumers, students and even children. In this past decade, however, that flow has been reversed. Now it is consumers, students and children who are leading the way, with early adopting adults and nimble small to medium size businesses following, and it is the larger institutions who are, frankly, the laggards. Our initial response might be to dismiss this trend as not really relevant to the issues of business. After all, if there really were useful productivity gains here, surely we would already be investing in them. Isn’t it far more likely that this proliferation of consumer services, social sites, and interactive games is simply digital entertainment which, if anything, should be banned from corporate computing? In a word, No.In two words, emphatically No. What is transpiring is momentous, nothing less than the planet wiring itself a new nervous system. If your organization is not linked into this nervous system, you will be hard pressed to participate in the planet’s future. To be more specific, amidst the texting and Twittering and Facebooking of a generation of digital natives, the fundamentals of next-generation communication and collaboration are being worked out. For them, it is clear, there is no going back. So at minimum, if you expect these folks to be your customers, your employees, and your citizens (and, frankly, where else could you look?), then you need to apply THEIR expectations to the next generation of enterprise IT systems. But of far more immediate importance is how much productivity gains businesses and governments are leaving on the table by not following the next generation’s lead. Think about how effective you are as a consumer and how much you can accomplish from your kitchen table on a Saturday or Sunday. Have a question? Google it or ask your social network. Buying a car? Go to the Web and learn more about the dealer’s price margins than the salesman will know. Kids looking at colleges? No more sending away for brochures like we used to—link right into the admissions department, and let them link right into to your child’s world. Medical worries? Not only is there superb information on the Web, but whatever your illness, there are communities out there who are already sharing their lessons learned about it. Or on happier notes, do you have a passion for cooking, or golf, or drama, or origami, or toy soldiers? You are only a click away from founts of information and a host of willing collaborators. In sum, putting all this in the context of our prior decades living on the planet, one can only say, How cool is that! OK, so why are we so slow to pick up the ball in business? Why do we still rely on e-mail to communicate with our employees? Why is it so hard to implement new technology? Why are our legacy systems so expensive? How do we get out from underneath all this cost? Why aren’t the applications that are critical to any organization as easy to implement as an app on an Android device or the iPhone? Why do consumer applications feel so much cooler than those in our organizations? Why is it — as Tony Zingale from Jive recently said — that we know more about what our high school girlfriend had for dinner than what is going on within our organization? How do we uncork the knowledge that is bottled up in the heads of our employees? What the heck is holding us back? Enterprise IT 1.0: Systems of Record The answer, in part, is our mental model of Information Technology. Those of us old enough to have senior management positions understand enterprise IT through the lens of data processing. That is how it grew up around us and we grew up with it. We spent the last half of the 20th century building up this capability from rows of punch cards that could process census data to global information systems that capture every dimension of our commercial landscape, from financial transactions to human resources to order processing to inventory management to customer relationship management to supply chain management to product lifecycle management, and on and on. These are the great systems of record, and like the interstate highway systems of a prior generation, they have paved the way for an enormous economic expansion. Indeed these information highways have enabled so much outsourcing of business processes that they have shifted the balance of economic power globally, with China and India being the primary beneficiaries, and Western Europe and Japan suffering the greatest short term consequences. This, in turn, is creating great new growth markets among a host of developing economies, complementing the well funded but more mature markets of the developed economies. But most important of all, the thing to register about systems of record is that they are mostly and largely complete, particularly within larger organizations. Are they perfect? No. But these systems of record are no longer a source of competitive differentiation for organizations. They are a necessary condition of doing business. Once you have an interstate highway system, the era of the great build out comes to an end, and the era of maintenance comes to the fore, and that is precisely what has happened with enterprise IT as we have known it. As a result, this past decade has been one of increasing optimization, led by IT budget cuts as funds are transferred to other uses within the enterprise, and led technologically within IT by virtualization, cloud computing, and ever more outsourcing. And that is where we stand today. So why would anything change? The Next Stage of Enterprise IT: Systems of Engagement The answer lies in the dynamics of the very outsourcing-driven global economy that systems of record have enabled. Under its globalizing influence, enterprises of all sizes and shapes have been forced to sharpen their competitive advantage or suffer commoditization of the goods and services. Companies are expanding their reach both organically and through acquisitions. This means they have to focus more resources on their core businesses, core competences, and core differentiation. As a result, few business transactions any longer involve just one vendor; more and more require the coming together of supply chains, delivery chains, customer support services, partner ecosystems and the like. And this is the key point to register: Business has become much more collaborative than ever before, if for no other reason than it has had to in order to make these chains of relationships actually work. And that brings us full circle back to our IT-enabled consumer experiences, which are deeply collaborative, highly effective, and astoundingly efficient. In the new global economy, business needs these very same capabilities for itself. What some are calling the consumerization of enterprise IT is not some sop thrown to the millennial generation swelling our work forces but rather a next wave of productivity gains to be garnered from investing in a next wave of IT. Only this time around, instead of investing in automating first level task workers at the edge of the enterprise with various transaction processing applications, and instead of informing executives at the top of the enterprise with various business intelligence applications, the focus instead will be on empowering the middle of the enterprise to communicate and collaborate across business boundaries, global time zones, and language and culture barriers, using next-generation IT applications and infrastructure adapted from the consumer space. What will enable this transformation are Systems of Engagement that will overlay and complement our deep investments in systems of record. Systems of engagement begin with a focus on communications. We grew up with letters, phones, telexes, and faxes, and grew into email, shared text databases like Lotus Notes, portals, web sites, and mobile phones. Now we are going to incorporate a third generation of communications, based on 1) connecting people in real time; 2) smart and geographically-aware mobile devices; and 3) ubiquitous and cheap bandwidth. These communication capabilities will also be complemented with new collaboration capabilities. These are IT-enabled services that allow groups of people to interoperate both synchronously and asynchronously, and they include wikis, collaborations tools, chat, crowd-sourcing, web conferencing, video streams, video conferencing, and similar services. And as cultural and language barriers become more and more important to overcome and transcend, high definition real time video telepresence sessions and the like will complement and in some cases replace the inevitable round of international trips required to make global commerce really work. If you are dependent upon suppliers or distributors or partners to deliver your fundamental value proposition to your customer — if, that is, you are in the technology sector, or health care, or financial services, or consumer packaged goods, or retail, or education, or government, or energy, or aerospace and defense, or travel and hospitality, or media and entertainment, or marketing and advertising, or anything else of such ilk—then who are we kidding? You have to grab onto the new communication and collaboration systems or you will simply end up as roadkill.
- Main Points: The importance of the digital value chain Sequential Story: Paint the picture of exposure, consumption, and the value chain What is (D) or What will be (U): U Analytical or Emotional connection: A Script: A new approach that understands the impact and requirements of the digital value chain. The value chain concept has been around for many years and consists of the activities that create and build value and gives focus to the activates that create value. Correspondingly, the transformation of business to the digital world introduces a new value chain that delivers value from your existing backend services to the user or customer. In the world of digital business, its not just about making services available, but also about making services easy to consume. Ridiculously easy to consume. The challenge is not one of integration but service exposure and consumption. Making services easy to use to build the apps of today whether through internal or external developers. Integration does expose services but not in a way that is easily consumable by a broad group of developers. And consumption is what provides ever expanding business value The digital value chain encompasses the entire process and participants and addressing only some aspects will at best constrain success. So how does IT deliver on the promise of digital business? How can it address all these new requirements that add to what they already have to manage? Background: http://economictimes.indiatimes.com/definition/value-chain Definition of 'Value Chain' A value chain is the whole series of activities that create and build value at every step Definition: A value chain is the whole series of activities that create and build value at every step. The total value delivered by the company is the sum total of the value built up all throughout the company. Michael Porter developed this concept in his 1980 book 'Competitive Advantage'. Description: The significance of the value chain: The value chain concept separates useful activities (which allow the company as a whole to gain competitive advantage) from the wasteful activities (which hinder the company from getting a lead in the market). Focusing on the value-creating activities could give the company many advantages. For example, the ability to charge higher prices; lower cost of manufacture; better brand image, faster response to threats or opportunities. What is the value chain made of? Porter defines the value chain as made of primary activities and support activities. Primary involves inbound logistics (getting the material in for adding value by processing it), operations (which are all the processes within the manufacturing), outbound (which involves distribution to the points of sale), marketing and sales (which go sell it, brand it and promote it) and service (which maintains the functionality of the product, post sales). The support functions which feed into all the primary functions are the firm infrastructure, like MIS which allows managers to monitor the environment well; Human Resource, which develops the skills needed to steer the company well; procurement to buy/ source goods at the right price, which increasingly takes importance because of difficult economic conditions and technology, which could give the firm speed, accuracy and quality. Both these allow the firm to charge a margin, which partly comes from the value addition of the primary and support functions and partly from the advantage that the company gains due to communication of the value addition to the consumer (brand image, faith, trust and so on).
- Main Points: Apigee Edge addresses the complete value chain Sequential Story: Move from why Edge (our differentiators) to exploring the product What is (D) or What will be (U): U Analytical or Emotional connection: A Script: As you can see, Edge delivers benefits across the digital value chain. API Services enable exposure of backend services in a way that developers can consume easily. Developer Services provide the tools, processes, and collaboration for a successful developer program And Analytics Services provide metrics and visibility across all aspects of the value chain
- Apigee Edge also helps a digital business focus on the entire API lifecycle. Edge will become the layer that provides a consistent façade that will save the technical team hours of development, AuthN and AuthZ at each point of interaction, API transformation & mediation, and will provide the ops team with consistent, auditable API traffic reports. Context for [24]7: What technical challenges are they solving with Apigee? Edge will become the layer that provides a consistent façade that will save the technical team hours of development, AuthN and AuthZ at each point of interaction, API transformation & mediation, and will provide the ops team with consistent, auditable API traffic reports. How had they dealt with these in the past? Inefficient, silo-ed efforts that were not reusable has been causing a cycle of Herculean effort by skilled, dedicated teams that they are churning through rapidly. The HR team noted that a standardized platform that enables their developers to be more effective will help them with retention efforts. Main Points: Not just about building simple APIs that proxy traffic from clients to backend systems *** Use this slide as a way to segue into specific features or product components depending on the customers’ interest, but frame them as part of this overall lifecycle *** Build Quickly build enterprise class APIs Enable multiple project teams to build apps and APIs independently Use the right tool for the job at hand Isolate dev. teams from production systems Release new APIs without disruption Use Publish APIs to partners and developers Create developer communities around APIs Offer custom rate plans to monetize APIs Secure APIs to protect against intrusions Analyze usage and traffic patterns Run Handle traffic growth while maintaining application performance Expand access to APIs from multiple geographies Protect backend systems from traffic spikes and DDOS attacks Roll-out or rollback changes in production without downtime Operate on-premises at cloud scale Scale for peak without incurring fixed costs
- Main Points: Summarize API services part of marketecture Sequential Story: Summarize what we have seen What is (D) or What will be (U): U Analytical or Emotional connection: A Script: The capabilities that we’ve just described are part of what we call API Services. They provide the base for API-driven digital business. Most importantly they combine the best of Internet scalability and addressing dynamic demand with a rock-solid, flexible and secure enterprise grade foundation. Background Info: After all, most of the benefits of the Cloud quickly disappear when the wrong architecture is implemented or the wrong technology is used. For instance, a monolithic application that uses DRBM can be deployed on Amazon AWS, and doesn’t necessarily make it more scalable than it was when deployed on static hardware in a data center. Apigee Edge has been architected from the bottom up to support multi-tenancy. Multi-tenancy also enables the on-premises customer to bring the flexibility and cost efficiency offered by Apigee Cloud into their data center. Architecture Design Principles APIs Everywhere - Components should communicate via APIs Management from command line and UI functions should leverage them. Dependencies Matter - Components should be able to function and scale independent from each other, minimizing and controlling dependencies and using abstract interfaces. Eventual Consistency - Embrace availability and partitioning tolerance across all critical components. Asynchronous Execution - If something can be done asynchronously, it must. Execution Partitioning - Logically separate execution and allocated capacity. Favor multi-tenancy. Data Partitioning - Logically separate data to facilitate scalability, processing and multi-tenancy. Everything Fails - The platform must keep operating even if part of it is unavailable. Favor graceful degradation and self-healing. Analytics and Metrics - Measure, analyze, improve. Everything must run on the cloud and on-premises - Cloud and on-premises deployment are equally important. Multi-tenancy - Capabilities are multi-tenant by design.
- Main Points: Flexibility to develop APIs in many different ways Sequential Story: Now address enterprise flexibility What is (D) or What will be (U): U Analytical or Emotional connection: A Script: As for flexibility, Edge enables you to develop APIs in a number of ways whether it is with java, python, javascript, or with node.js Very popular today, is development in node.js. Edge can integrate node.js applications and be used to create APIs and build mash-up services Edge also works with Apigee-127, a model-first toolkit for building rich, enterprise-class APIs in Node.js on your laptop With Apigee-127 developers focus on implementing the API's core logic in Node.js. Run the API entirely locally, in conjunction with Apigee Edge, or entirely on Apigee Edge Background Info: About Node.js Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. Node.js is an open source, cross-platform runtime environment for server-side and networking applications. Node.js applications are written in JavaScript, and can be run within the Node.js runtime on OS X, Microsoft Windows, Linux, FreeBSD, and IBM i. Node.js provides an event-driven architecture and a non-blocking I/O API that optimizes an application's throughput and scalability. These technologies are commonly used for real-time web applications. Node.js uses the Google V8 JavaScript engine to execute code, and a large percentage of the basic modules are written in JavaScript. Node.js contains a built-in library to allow applications to act as a Web server without software such as Apache HTTP Server or IIS. About 127 Apigee 127 is a collection of open source modules, including Volos, for Node.js that help us build APIs locally on the laptop and then deploy to the cloud. It also includes a tool called Swagger that is used to documnent the API spec Apigee-127 is toolkit for modeling & building rich, enterprise-class APIs in Node.js on your laptop. The focal point of Apigee-127 is the Swagger 2.0 specification for defining and describing an API model. From the Swagger model you can generate clients, servers and interactive documentation for your API. Apigee-127 is a toolkit that enables API developers to quickly build an API in Node.js with a Model-first approach with the Swagger 2.0 standard The output of Apigee-127 is: A Node.js application which is a single API (proxy) A Swagger 2.0 spec describing the API (proxy) The resulting Node.js application can be deployed to any platform that runs Node.js, including: Apigee Edge, Apigee Developer and OPDK installations Any Node.js PaaS – Heroku, Amazon EB, Cloud Foundry, etc. Apigee-127 includes: The Swagger 2.0 Editor (https://github.com/wordnik/swagger-editor)—Built by Apigee for the API development community, the editor provides a great side-by-side authoring experience for API specs in Swagger. On the left you have a YAML editor and on the right a preview of your documentation. Swagger tools (https://github.com/apigee-127/swagger-tools)—Node.js libraries to take a Swagger spec and provide message validation and routing to your custom code. Volos.js (https://github.com/apigee-127/volos)—Open source libraries that provide API services such as caching, quota, and OAuth. Apache Usergrid (http://usergrid.incubator.apache.org)—The open source version of Apigee’s Backend as a Service. Benefits Enable them to build robust APIs faster and easier Fast API Development on your local machine Zero to enterprise-class APIs in minutes: Leverage Open Source Node.js policies for enterprise-class APIs Deploy 127 APIs to Apigee or PaaS / platform of their choice Connect to enterprise backend systems with Apigee Node.js Connectors 127 provides a design-first toolkit for building APIs in a consistent manner API Implementations API Policies APIs described/documented in a standard model – Swagger 2.0 APIs built in a consistent manner are easier to manage! 127 has three modes of operation: Independent of Edge - running On-Premises and operating completely independent of Edge Remote – Running externally but consuming Edge services remotely (see below) On Edge - Running as a Node.js application deployed inside Edge & consuming Edge services directly Swagger™ is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters, and models are tightly integrated into the server code, allowing APIs to always stay in sync. With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability.
- Apigee’s runtime processing capabilities are enforced through two means: configurable policies and flexible scripting. These two things can be combined into a processing pipeline that enables both enforcement of the runtime rules of engagement with the API and the transformations required to get from the clean REST API to the interface exposed by the back end system.
- Flows are the basic building blocks of API proxies. Flows enable you to program the behavior of an API by letting you configure the sequence in which policies and code are executed by an API proxy. As shown in the diagram below, API proxies define request and response Flows. The request and response Flows are subdivided into proxy and target segments. Each segment is subdivided into 3 Flow 'stages': - PreFlow: Always executes before any conditional Flows. - Conditional Flows: One or more Flows, each of which has an associated Condition. Only one Flow executes per transaction--the first Flow whose Condition evaluates to true. When you implement 'branching' logic for an API - PostFlow: Always executes after any conditional Flows. - PostClientFlow: An optional Flow that executes after the response message has been sent to the requesting client app. (This is a specialized Flow, and only MessageLogging policies can be attached to it.)
- Main Points: Today’s end-users demand a higher level of functionality, personalization and experience from their apps. Its not just sufficient to expose your APIs you need to provide consumable APIs that developers love to use and provide the capabilities they are asking for. Script: Example of an app flow: Single cart and product catalog accessible to and optimized for all app channels Up-to-date inventory and pricing New services Shopper identity, preferences Wish lists Reviews Push notifications Location Normalization and optimization of data Price, Inventory, Promotion App and enterprise security Secure handling/PCI compliance Traffic management, protocol transformation Additional thoughts. Involves more than API Management. Exposing your API’s is not enough. Need to enable your API’s to be consumable. Need your APIs to provide capabilities that App developers and end-users want. Also need to be able to capitalize on the data that you have on your user and activate it for use to make valuable business decisions.
- Main Points: Reveal marketecture with API and Dev Services Sequential Story: Summarize developer services What is (D) or What will be (U): U Analytical or Emotional connection: A Script: Developers are a critical part of a digital solution and friction-free adoption and streamlined learning are key to their success. Apigee Edge delivers the functionality needed to be successful with any developers with Developer Services that enable a great developer experience that increases API adoption, simplifies learning about your APIs, and increases the business value of your APIs. Background Info: Developer Services The developer is the key driver of success in the digital economy and developer adoption and the developer communities are critical requirements for widespread use of your API. One of the best ways to make developers successful is to put them in touch with each other – so that they can share information, tips and tricks, and creativity in working with your API. They often use the API in ways that have never been possible and have yet to be imagined. That’s why some of the most successful software companies have the most vibrant developer communities. Apigee Edge includes Developer Services, which enable a great developer and community experience that accelerates API adoption, simplifies learning, and increases the business value of APIs. A developer portal provides a community for developers with the resources needed to learn about the API, become a registered developer, and share challenges and solutions with peers and with the enterprise. Modeling and Developer Management enables fast developer on-boarding with registration and app-key generation. Interactive API documentation simplifies learning, testing, and evaluation of APIs. An API Console enables developers to easily access, explore and test APIs without incurring any setup overhead. The API Console makes it easy for developers to learn which of an enterprise’s APIs are best suited to their task increasing adoption of, and satisfaction with, your APIs. API monetization increases the business value of APIs with revenue models based on fees, freemium, and revenue sharing. Monetization capabilities enable the API provider to manage revenue plans for individuals, groups of developers, and an entire developer community—and even inside the enterprise by enabling chargebacks from business units that use company APIs.
- Main Points: Apigee Enterprise is the only truly self-service offering from developer sign up to management of APIs and policies to debugging of the end to end API proxy. Script: Whether your API is for internal of external developer consumption, your developers can easily request access keys, your architects can setup the key approval model based on your preferences or easily approve access and the developer is ready to start developing.
- Main Points: Monetization services has lots of capability Sequential Story: Articulate flexibility of monetization services What is (D) or What will be (U): U Analytical or Emotional connection: A Script: Monetization services, that charge the developer – the user of the API, enable a variety of business models Revenue Sharing Model: Paying developers for the usage of your APIs based on purchase of your services. Fee-based Model: Developer pays you for API usage Freemium Model: An offer for an initial set of usage for free, and then charge as the developer’s API usage grows You can set limits of use and manage notifications for developer plan purchase, expiration, and renewal, And provide an integrated workflow for developers to purchase plans, receive bills and notifications It also supports pre-paid and post-paid billing and tax calculations Monetization services can also be used inside the enterprise to enable chargebacks from business units that use centrally developed and managed APIs. Monetization models can be customized to meet complex requirements: Background Info: Overview of Monetization in the Developer Portal Monetization features in the Developer Portal are controlled by Drupal modules. When you activate Monetization for your organization, these Monetization-specific Drupal modules are automatically added to your developer portal. You must configure these modules to enable Monetization features. For example, Monetization features in the developer portal integrate with the Worldpay payment system using a Drupal module, which enables your developers to make credit and debit card payments, set up prepaid and recurring payment plans, and set up more billing options. To make full use of Monetization features, your developers must complete additional information in their Developer Portal user settings. For example, to subscribe to a rate plan you've set up, developers must enter their company information and accept your terms and conditions. Monetization also gives developers self-service access to billing, reports, product catalogs, and other Monetization-specific settings. Monetization includes additional Drupal roles that give you control over access to Monetization administration and functionality in the Developer Portal. For example, we deliver the Monetization Administrator and Finance Administrator roles, which are preconfigured to provide access to specific Monetization functionality. As an API provider, you need an easy-to-use and flexible way to monetize your APIs so that you can generate revenue for the use of those APIs. Monetization, a feature of Apigee Edge Developer Services, solves those requirements. Using monetization, you can create a variety of rate plans that charge developers for the use of your APIs bundled into packages. The solution offers an extensive degree of flexibility: you can create pre-paid plans, post-paid plans, fixed-fee plans, variable rate plans, "freemium" plans, plans tailored to specific developers, plans covering groups of developers, and more. In addition, monetization includes reporting and billing facilities. For example, as an API provider, you can get summary or detailed reports on traffic to your API packages for which developers purchased a rate plan. You can also make adjustments to these records as necessary. And you can create billing documents (which include applicable taxes) for the use of your API packages and publish those documents to developers. You can also set limits to help control and monitor the performance of your API packages and allow you to react accordingly, and you can set up automatic notifications for when those limits are approached or reached. Monetization provides an API that is integrated into Edge API Services and a management user interface for API providers that is integrated into the Edge management UI. The management user interface calls the monetization API. Monetization also provides a developer portal through Edge Developer Services. The developer portal includes monetization-related content that an API provider publishes for viewing by a developer, such as a catalog of available API packages and rate plans for each package. As an API provider, you can take advantage of the monetization features in the developer portal or integrate monetization features into your own developer portal.
- Script: Here are some examples of our customers that have established API monetization models for their developers: Pearson, the largest education company and the largest book publisher in the world, offers developers a Freemium model for some of its API products. As you can see in this example, it is based on number of API calls per month, where they are free for an initial range, and then need to be paid for. The second example, with Thomson Reuters showcases how this customer has implemented an internal monetization policy. Any business unit utilizing the Finance and Risk API has to transfer funds in the form of Internal Chargebacks to the API provider business unit. Driving external revenue from your assets is best showcased here with Earth Networks. As you can see, they have a fee-based model with multiple packages that offer a defined set of API products, and can be leveraged by both, individual app developers or partners and companies that need to use these APIs for their enterprise apps.
- Script: Developers can stay on top of their API transactions – explore, compare and buy API products, manage limits and usage and carry out payments and other financial transactions, all within the Developer Portal.
- Main Points: Reveal marketecture with Analytics Services Sequential Story: Wrap up functionality for analytics What is (D) or What will be (U): U Analytical or Emotional connection: A Script: The analytics capabilities we have been discussing are provided by Edge Analytics Services. They provide the visibility across the value chain that is necessary to monitor, measure, and manage success. Let’s take a look at a few Analytics Services have helped a number of customers Background Info: Analytics Services Success can only be determined with sufficient understanding and insight. The API Team represents many functions of the enterprise and each has a corresponding measure of success. Operations needs to understand traffic management, developers want to know about App adoption and performance, and the API program owner needs to understand if the program is achieving business success. Edge Analytics Services enable end-to-end visibility across the digital value chain with operational, developer, App performance, and business metrics that are necessary to monitor, measure, and manage success. Business Metrics are key metrics in a business context for monitoring and measuring API program goals and helping to make smart informed business decisions.. App performance monitoring measures app performance and usage on different devices, carriers, and platforms, and even measures the performance of different versions of an app. Grow user engagement by understanding the technologies, performance, and stability of the most and least adopted technologies of your users. Developer metrics provide the means to monitor usage and performance of the developers, apps, and APIs in an enterprise ecosystem. Identify a developer program’s top developers and apps, measure developer engagement, and view API traffic by developer to better understand the keys to developer program success. Ops Analytics monitor the health and performance of the APIs and your API ecosystem, plan for traffic spikes, identify slow and error-prone APIs, find root causes, and understand traffic anomalies.
- Main Points: Highlight what visibility across the value chain means to the API team Sequential Story: Now provide more detail on Edge analytics benefits What is (D) or What will be (U): U Analytical or Emotional connection: A Script: This means that the cross functional API team has the information they need relative to each members role. For example: API product managers are looking to understand program adoption and how API use can be improved. Business owners want to understand where to invest and how the program is effecting bottom line revenue. Operations needs to monitor the health and operation of the APIs as they are used by apps and developers Lastly app developers need to know how their apps are performing, the impact of the API on the app and what changes might help them.
- Main Points: Analytics are not only comprehensive but also rich Sequential Story: Now talk about the depth of richness analytics includes What is (D) or What will be (U): U Analytical or Emotional connection: A Script: Edge includes a very rich set of dashboards that provide operational, developer, app, and business metrics. Custom reports enable you to select, combine, filter, and drill down into specific API metrics. Reports can be viewed in the UI, exported to CSV, PDF, or PNG files. In addition, you can create your own analytics dashboard and populate it with custom reports that you select. Even more valuable is how you can create custom metrics by wiring together metrics and API Services. For example, a financial services customer is extracting transaction data from the request payload and combining it with the developer and app name to understand which developers and apps are delivering the most revenue. Background Info: Using the Analytics Services API, you can access a wide variety of operational and business data that flows across your APIs You can also create custom metrics by wiring together features of Analytics Services and API Services. Custom reports The custom report feature lets you select, combine, filter, and drill down into specific API metrics. You can generate reports that contain the exact data that you want to see. Reports can be viewed in the UI, exported to CSV, PDF, or PNG files. In addition, you can create your own analytics dashboard and populate it with custom reports that you select. You can request daily summary reports Use policies to extract custom data from a request and feed that data to the Edge Analytics system You can also create custom metrics by wiring together features of Analytics Services and API Services. For example, you can create a policy designed to extract certain information from an API (from request headers, for instance) Proxy resource performance view You also can track performance metrics for individual URIs (resources) for a specific API proxy. This view lets you plot trends in traffic, response time, and other metrics for each individual resource. You can toggle the dashboard between the API program view, which gives you a sense of overall API performance, and API top performer view, which tells you about your top performing APIs, apps, developers, and API products. You can select a time interval (hour, day, week, month) over which the data is plotted or specify a custom timespan. You can also mouse over any point on a plot to see in greater detail what was happening at that point. Dashboards The Endpoint Perfromance dashboard tracks how your endpoint servers behave from Apigee's point of view. This dashboard gives you visibility into what kind of errors or latency is observed from specific endpoint servers, allowing operation teams to better understand their backend systems. Apigee Dashboard API Program View - Monitors how your APIs are growing, the engagement of your developers, and the rates of developer adoption. Top Performance View - Monitors API traffic growth patterns, including error rates across specific periods of time. Gives you a summary of to The API Proxy Performance dashboard tracks how much time API proxies spend processing requests and responses. This dashboard lets you visualize the network latency between Apigee Edge and backend servers. The Cache Performance dashboard lets you see at a glance the value of your Apigee Edge cache. The dashboard helps you visualize the benefit of the cache in terms of lower latency and reduced load backend servers. The Latency Analysis dashboard can alert you to any latency issues your API proxies may be experiencing. It displays latency measurements down to the window of a minute, highlighting the median, 95th percentile, and 99th percentile values. The Error Analysis dashboard tells you about error rates for API proxies and developer apps. The Partner Engagement dashboard tells you which of your partner developers are generating the most API traffic. For each of your developer partners, you can find out who is generating the most API traffic and the most errors. For example, if a particular developer's app is generating a lot of errors relative to other developers, you can proactively address the problem with that developer. The Traffic Composition dashboard measures the relative contribution of your top APIs, apps, developers, and products to your overall API program. Use the report to detect business problems such as lower traffic trends or diminishing contribution from key apps and developers. Based on this data, you can decide what corrective action to take. You can also get early notification of new entities that contribute to API traffic, and take actions to respond — for example, you can determine which new developers are highly contributing and include them in nurturing programs. The Business Transactions Dashboard lets you monitor and visually compare traffic for specific API patterns across multiple API proxies. This information helps you understand changes in API traffic that might be caused by specific business, marketing, or partner events. For example, suppose that your marketing team hosts a program that drives customers to a specific site. The URI pattern for that site will experience an increase in traffic, giving the team a way to measure the impact of the program in real time. The Geo Map dashboard tracks traffic patterns, error patterns, and quality of service across geographical locations. You can view information about all your APIs, or zoom in on specific ones. This dashboard helps you assess: API growth trends - Use the Traffic metric to see where your traffic is coming from. By using different time periods you can see which countries generate the most traffic at which times. You can also record traffic rates over different time periods to see trends in growth. Error trends - Use the Error Count metric to see where where API errors are coming from. By using different time periods you can see which countries generate the most errors at which times. You can also record error rates over different time periods to see trends in growth. Quality of service - Use the Average Response Time and Average Target Response Time metrics to see how your backend services are performing by country. The Devices dashboard tells you about the devices and servers that are being used to access your APIs. It lets you spot trends in how users are accessing your APIs. For instance, you might notice that traffic from one type of device is increasing, while another is going down, and then decide if the change requires any action or not. The Custom Reports dashboard lets you display up to four custom reports on one page. This dashboard is intended to give you a "real time" view of your custom report metrics. The time-scale for this dashboard ranges from 5 minutes to one hour. The dashboard can include any custom reports that you previously created — including reports that use custom variables, drill-downs, metric correlations, and filters.
- Main Point Apigee for iPad provides access to the dashboard on the go. Sequential Story: You are not constrained by where you view analytics either. What is (D) or What will be (U): U Analytical or Emotional connection: A Script Edge also provides an iPad App that gives you analytics on the go. Its beautifully designed and works very similar to the desktop version and is available at the iTUnes App store
- Main Points: Introduce full marketecture Gain end-to-end visibility and control of the entire mobile value chain from app to back-end systems Make data driven decisions using intuitive and easy-to-use actionable dashboards and reports Meet virtually any analytics need by creating custom reports using any attribute that describes your traffic Sequential Story: Summarize the value of Edge What is (D) or What will be (U): U Analytical or Emotional connection: A Script: With our discussion of analytics services, we complete our overview of Apigee Edge. <CLICK> With API Services that help you build, manage, scale, and secure APIs and Apps And Developer Services that help you increase developer adoption and the value you get from your APIs And lastly with Analytic Services that enable you to monitor, manage, and measure success across the digital value chain. Background Info: The companies achieving digital business success today are not only digital native startups pursuing new business models but also the traditional businesses in existence long before the emergence of the digital economy. The challenge for business is no longer if or when to embrace digital initiatives but rather how to become a digital business. The answer to this challenge is to extend a business’ data and services to ever present digital devices while translating core strengths into unique digital advantages. Many competitive advantages like size, location, and even business model that existed in the traditional enterprise are no longer relevant. Easy access to data and services, seamless and intuitive experiences in multiple channels, and the agility to respond quickly to changing customer and market demands are today’s competitive advantages. Digital business success requires an approach that addresses all aspects of the digital value chain and that complements existing enterprise infrastructure; a solution that enables the business to meet the demands of today’s customers, partners, and employees, to support applications on a wide range of devices, and to enable innovation and new strategic partnerships. Extending across the entire digital value chain includes providing access and protection of internal data and systems, enabling API modeling and design, providing the scalability and reliability of API execution, and the care and feeding of the developers using your API to build the apps that spur innovation and extend the reach of your business and brand. Metrics that increase visibility of the interactions across the value chain are needed to separate success from uncertainty and allow you, just as you do with your supply chain, to evaluate where improvements need to be made. Apigee Edge enables digital business acceleration with a unified and complete platform, purpose-built for the digital economy. Edge simplifies managing the entire digital value chain with API Services, Developer Services, and Analytics Services. API Services unites the best of Internet and enterprise technologies with API management, BaaS, security, and programming extensibility to provide rock-solid reliability and enterprise-grade flexibility Developer Services enable a great developer and community experience that accelerates API adoption, simplifies learning, and increases the business value of APIs. Edge Analytics Services enable end-to-end visibility across the digital value chain with operational, developer, App performance, and business metrics that are necessary to monitor, measure, and manage success.
- The rules of engagement for APIs include four key groups of functionality that can be configured to provide a very strong security framework. Two of those groups – Authentication and Authorization – are implemented during runtime API processing to actively manage API requests in real time. <explain> The other two groups – User Management and Infrastructure – work in the background to ensure that the Apigee environment itself is stable, secure, and performs well. <explain>
- Main Points: Representative of a large retail business. The check boxes are highlighting the capabilities associated with the Apigee security capabilities that this type of consumer would be leveraging/taking advantage of. Notice that not all capabilities are required for every business use case. Apigee is built from the ground up to address real world business cases and security is part of those business cases.