Index
A
- AaaP (see API as a Product)
- advice, collecting, Governance
- Agile, BDUF and, Coupling Costs
- agility, API landscapes and, Velocity
- Alexander's cultural mosaic, Enabling Alexander’s Cultural Mosaic-Enabling Alexander’s Cultural Mosaic
- Alexander, Christopher
- Amazon (see AWS) (see Bezos Mandate)
- API archaeology, API Archaeology
- API architect, Technical Roles
- API as a Product (AaaP), The API as a Product-Summary
- API designer (team role), Business Roles
- API discovery (see discovery (API pillar))
- API economy, Vulnerability
- API evangelist (team role), Business Roles
- API gateway, Using frameworks and tools
- API management
- API management (generally), The Challenge of API Management-Summary
- API Mandate (see Bezos Mandate)
- API pillars (see pillars, of API)
- API product manager (PM), Business Roles
- API protocol, API Landscapes as Language Landscapes
- API simulation (sandbox), for testing, API testing tools
- API style, API Landscapes as Language Landscapes
- API technical writer, Business Roles
- API the APIs concept, API the APIs
- APIOps, Deployment automation
- APIs (generally)
- as only product, Customer Onboarding
- business goals and, The Business of APIs
- decoupling interface from implementation, Interface, implementation, and instance
- definition, What Is an API?, API Archaeology
- ease of use as design element, Making APIs easy to use
- ecosystem of (see landscapes, API)
- maturity stages, API Maturity Stages
- multiple meanings of term, The Challenge of API Management
- safety in design of, Making It Safe and Easy-Making APIs safe to use
- search engines and, API discovery
- Apple
- Apple App Store applications, The Platform Principle
- archaeology, API, API Archaeology
- assumptions, in design stage, Design
- attack surfaces, Vulnerability
- audience, knowing your
- authorization, in decision process, Authorization, Key decisions for security governance
- automation
- availability, GraphQL and, Volatility
- AWS (Amazon Web Services), Matching People’s Needs-The Bezos Mandate
B
- backend developer (BE), Technical Roles
- Backend for Frontends (BFF), Volatility
- backend simulation, for testing, API testing tools
- backward compatibility, versioning and, Versioning
- Baker, Van
- balanced scorecard, Defining an API Objective
- BDUF (big design up front), Coupling Costs
- BE (backend developer), Technical Roles
- Bezos Mandate, The Bezos Mandate, Visibility, Vulnerability
- Bezos, Jeff, Scope of optimization, Matching People’s Needs
- BFF (Backend for Frontends), Volatility
- big design up front (BDUF), Coupling Costs
- Bing, Vocabulary
- Bloch, Joshua
- boundaries
- Brittain, Mike, Velocity
- Brooks, Fred
- Brown, Tim
- business goals, The Business of APIs
- business roles, teams and, Business Roles
- business strategy, Viable Business Strategy
C
- canary testing, Velocity
- CDN (Content Delivery Network), The Platform Principle
- Center for Enablement (C4E), The Center for Enablement-C4E Team and Context
- centralization, Vulnerability
- centralization/decentralization binary
- centralized integration, API Management at Scale
- centralized storage, Visibility
- centralized/authoritative governance, results-oriented governance vs., Governing Decisions
- challenges, to decisions, Challenge
- change, Adapting your strategy
- (see also change management, continuous API improvement)
- adapting strategy to, Adapting your strategy
- API change velocity, API Change Velocity-Eliminating wasted effort
- create stage and, Stage 1: Create
- eliminating wasted effort to improving speed/safety of, Eliminating wasted effort
- incremental improvement, Incremental Improvement-Incremental Improvement
- maintain stage and, Stage 4: Maintain
- organizational design/culture and, Organizational design and culture
- tools for improving speed/safety of, Tools and automation
- velocity of, API Change Velocity-Eliminating wasted effort
- change management (API pillar), Change Management
- changing an API, Changing an API-Changing the Supporting Assets
- Chaos Monkey, The Center for Enablement
- chapters, roles and, Teams and Roles at Spotify
- choice generation, Choice generation
- Christensen, Clayton, The Business of APIs, Matching People’s Needs
- (see also Jobs to Be Done (JTBD))
- CI/CD (Continuous Integration and Continuous Delivery) tools, Tools and automation, Variety
- client simulation, for testing, API testing tools
- code, embedding interface description format in, Using frameworks and tools
- collaborative governance, Governance Pattern #3: Collaborative Governance
- complex adaptive systems, Complex adaptive systems
- complex systems, governance of, Governing Complex Systems-Complex adaptive systems
- compliance, C4E teams and, C4E Team and Context
- consistency, governance to encourage, Governing Decisions
- Content Delivery Network (CDN), The Platform Principle
- continuous API improvement, Continuous API Improvement-Summary
- API change velocity, API Change Velocity-Eliminating wasted effort
- changing an API, Changing an API-Changing the Supporting Assets
- changing the implementation, Changing the Implementation
- changing the instance, Changing the Instance
- changing the interface model, Changing the Interface Model-Changing the Interface Model
- changing the supporting assets, Changing the Supporting Assets
- coupling costs, Coupling Costs
- effort costs, Effort Costs
- eight Vs and, Maturity and the Eight Vs
- improving API changeability, Improving API Changeability-Coupling Costs
- managing change continuously, Managing Change Continuously-Eliminating wasted effort
- opportunity costs, Opportunity Costs
- continuous architecting, Principles, Protocols, and Patterns, API Landscape Journey, Maturity and the Eight Vs
- Continuous Integration and Continuous Delivery (CI/CD) tools, Tools and automation, Variety
- Conway's law
- Conway, Mel
- coordination costs
- corporate culture (see culture, organizational)
- costs, Governing Decisions
- coupling costs, Coupling Costs
- create stage of API product lifecycle, Stage 1: Create
- cultural mosaic, Enabling Alexander’s Cultural Mosaic-Enabling Alexander’s Cultural Mosaic
- culture, organizational
- customer onboarding
D
- dashboards, Visibility
- data dictionary, Vocabulary
- DDD (domain-driven design), Changing the Interface Model
- decentralization, Centralization and Decentralization
- decentralization and, Centralization and Decentralization
- decision blindness, Inception
- decision elements, Teams, The Elements of a Decision-Challenge
- (see also authorization; challenges; choice generation; implementation; inception)
- decision mapping, Decision Mapping-Decision mapping example: Tool selection
- decision points, maturity and, Decision Points and Maturity
- decisions (decision-making)
- API pillars as boundaries for, Introducing the Pillars
- authorization of, Authorization
- challenges to, Challenge
- choice generation, Choice generation
- decentralized vs. centralized, Centralization and Decentralization
- elements of, The Elements of a Decision-Challenge
- factors impacting, Centralization and Decentralization
- governance and effective decision management, Governing Decisions
- governance and management, Decisions
- governance and quality of, Governing Decisions
- implementation of, Implementation
- in interface design, Design
- inception, Inception
- selection from possible options, Selection
- standardization for security, Key decisions for security governance
- teams and, Teams
- declarative policies, for security implementations, Vulnerability
- decoupling delivery, Velocity
- defensive programming, Volatility
- Dell, Michael
- Deming, W. Edwards, Incremental Improvement
- dependencies
- dependent change, Changing an API
- deployment (API pillar), Deployment, Deployment-Volatility
- description formats, Using a design method, The interface and implementation relationship
- design (API pillar), Design-Key decisions for design governance, Design-Versioning
- design constraints, general standards vs., Standards
- design thinking
- design-time discovery, Design-time discovery
- developer experience (DX)
- developer portal, Documentation methods
- developer relations (DevRel), Business Roles
- development (API pillar), Development-Key decision for development governance, Development-Volatility
- DevOps, Deployment automation, Velocity
- DevOps engineer, Technical Roles
- digital footprint, Volume
- discovery (API pillar), API discovery, Discovery and Promotion-Key decisions for discovery governance
- distributed collection, Visibility
- distributed release management, Velocity
- diversity (see cultural mosaic)
- documentation (API pillar), Documentation-Key decisions for documentation governance
- developer experience and, Making APIs easy to use
- for API landscape, Documentation-Visibility
- interactive, Documentation methods
- investing in, Investing in documentation
- key governance decisions, Key decisions for documentation governance
- methods, Documentation methods
- publish stage and, Documentation, Stage 2: Publish
- realize stage and, Documentation
- risk reduction via warnings in, Making APIs safe to use
- teach don't tell method, Documentation methods
- tell don't teach method, Documentation methods
- domain-driven design (DDD), Changing the Interface Model
- domain-independent vocabularies, Vocabulary
- domain-specific vocabularies, Vocabulary
- Drucker, Peter
- Dunbar Level One/Level Two teams, Leveraging Dunbar’s Numbers
- Dunbar's number(s), Teams and Roles at Spotify, Leveraging Dunbar’s Numbers-Leveraging Dunbar’s Numbers
- Dunbar, Robin, Leveraging Dunbar’s Numbers
- DX (see developer experience)
E
- ease of use, Making APIs easy to use
- ecosystem, API (see landscapes, API)
- effort costs, for continuous API improvement, Effort Costs
- eight Vs of API landscapes, The Eight Vs of API Landscapes-Volatility, Maturity and the Eight Vs-Volatility
- encapsulation, Visibility
- enforcement, incentivization vs., Designing Your Governance System-Governance Pattern #3: Collaborative Governance
- enterprise information model (EIM), Vocabulary, Vocabulary
- enterprise service bus (ESB), The Platform Principle
- error messages, vocabulary and, Vocabulary
- Etsy, Velocity
- European Union (EU), Vulnerability
- evolutionary design, Volatility
- experimentation, corporate culture and, Supporting Experimentation
- explicit authorization, Authorization
- external APIs
- external dependencies, Vulnerability
F
- failure, innovation and, Supporting Experimentation
- Feinberg, Barbara
- frameworks, for development, Using frameworks and tools
- Frequently Asked Questions (FAQ) section, as part of documentation, Making APIs easy to use
- frontend developer (FE), Technical Roles
- functionality, What Is an API?
- (see also implementation)
- future, preparing for, Prepare for the Future
G
- general data protection regulation (GDPR), Vulnerability
- general principles, process instructions vs., Governance
- general standards, design constraints vs., Standards
- Genius Bar, Developer Experience
- goal alignment, Defining an API Objective
- Google
- Gore, William Bill
- governance, API Governance-Summary
- API landscape and, Governance
- basics, Governance
- centralization and decentralization, Centralization and Decentralization-Scale of operation
- change management decisions and, Key decisions for change management governance
- collaborative, Governance Pattern #3: Collaborative Governance
- company culture as implicit form of, Culture and Teams
- complex systems and, Governing Complex Systems-Complex adaptive systems
- consistency vs. innovation, Governing Decisions
- costs of, Governing Decisions
- critical features for governance system, Designing Your Governance System
- decision mapping, Decision Mapping-Decision mapping example: Tool selection
- decision-making quality and, Governing Decisions
- decisions and management choices, Decisions
- deployment decisions and, Key decisions for deployment governance
- design decisions and, Key decisions for design governance
- development decisions and, Key decision for development governance
- discovery decisions and, Key decisions for discovery governance
- documentation decisions and, Key decisions for documentation governance
- effective decision management and, Governing Decisions
- elements of a decision, The Elements of a Decision-Challenge
- foundational concepts, Understanding API Governance-Complex adaptive systems
- incentivization vs. enforcement, Designing Your Governance System-Governance Pattern #3: Collaborative Governance
- interface supervision, Governance Pattern #1: Interface Supervision
- machine-driven, Governance Pattern #2: Machine-Driven Governance
- monitoring decisions and, Key decisions for monitoring governance
- patterns, Designing Your Governance System-Governance Pattern #3: Collaborative Governance
- security decisions and, Key decisions for security governance
- strategy decisions and, Key decisions for strategy governance
- system design, Designing Your Governance System-Governance Pattern #3: Collaborative Governance
- testing decisions and, Key decisions for testing governance
- variety management as act of, Variety
- governance and, Complex adaptive systems
- graceful degradation, Volatility, Volatility
- GraphQL
- guidance
- guilds, Teams and Roles at Spotify
I
- immutability, Dealing with uncertainty
- implementation, Interface, implementation, and instance
- changing, Changing the Implementation
- create stage and, Stage 1: Create
- decisions, Implementation
- decoupling from interface, Interface, implementation, and instance
- defined, Interface, implementation, and instance
- interface and, The interface and implementation relationship
- implicit authorization, Authorization
- incentivization, enforcement vs., Designing Your Governance System-Governance Pattern #3: Collaborative Governance
- inception, of a decision, Inception
- incremental improvement, Incremental Improvement-Incremental Improvement
- information, decision-making and, Centralization and Decentralization
- infrastructure APIs, API the APIs
- infrastructure, C4E teams and, C4E Team and Context
- Infrastructure-as-a-Service (IaaS), The Bezos Mandate
- innovation
- instance, Interface, implementation, and instance
- integration testing, What needs to be tested?
- interactive documentation, Documentation methods
- interface
- API as, What Is an API?
- decoupling from implementation, Interface, implementation, and instance
- defined, Interface, implementation, and instance
- design (see design (API pillar))
- implementation and, The interface and implementation relationship
- Web architecture and, Principles, Protocols, and Patterns
- interface definition language, Coupling Costs
- interface description formats, Using a design method
- interface model, Changing the Interface Model-Changing the Interface Model
- interface supervision, Governance Pattern #1: Interface Supervision
- internal APIs
- International Organization for Standardization (ISO), Vocabulary
- ISO 639, Vocabulary
- iterative SDLC, The API Release Lifecycle
- Ivarsson, Anders
L
- landscapes, API, API Landscapes-Summary
- API archaeology, API Archaeology
- API management at scale, API Management at Scale-API the APIs
- API the APIs concept, API the APIs
- basics, More Than a Single API, API Landscapes-API Landscapes
- Center for Enablement and, The Center for Enablement-C4E Team and Context
- defined, API Landscapes
- eight Vs and maturity, Maturity and the Eight Vs-Volatility
- eight Vs of, The Eight Vs of API Landscapes-Volatility
- governance, Governance
- guidance lifecycle in, The Lifecycle of Guidance in the API Landscape
- guidance structure in, Structuring Guidance in the API Landscape-Structuring Guidance in the API Landscape
- language landscapes, API Landscapes as Language Landscapes
- lifecycle management in (see lifecycle management)
- management of, Managing the API Landscape-Governance
- maturity journey, API Landscape Journey-Summary
- platform principle and, The Platform Principle
- principles, protocols, and patterns, Principles, Protocols, and Patterns-Principles, Protocols, and Patterns
- proto-APIs and, API Archaeology
- scale and, Scale
- team building, Teams
- technical decisions, Technology
- understanding, Understanding the Landscape
- variety, Variety, Variety-Variety
- velocity, Velocity, Velocity-Velocity
- versioning, Versioning-Semantic versioning, Versioning
- visibility, Visibility, Visibility-Visibility
- vocabulary, Vocabulary-Vocabulary, Vocabulary-Vocabulary
- volatility, Volatility, Volatility
- volume, Volume, Volume-Volume
- vulnerability, Vulnerability
- language management, API Landscapes as Language Landscapes
- languages, API landscapes and (see vocabulary)
- Lashinsky, Adam
- last responsible moment, Opportunity Costs, Decision Points and Maturity
- lead API engineer, Technical Roles
- Lean, Variety
- libraries, dependency management problems and, Visibility
- lifecycle management
- API landscapes and individual APIs, API Landscapes
- API products and lifecycle pillars, API Products and Lifecycle Pillars-Decision Points and Maturity
- change management and, Change Management-Visibility
- decision points and maturity, Decision Points and Maturity
- deployment and, Deployment-Volatility
- design and, Design-Versioning
- development and, Development-Volatility
- discovery and, Discovery-Versioning
- documentation and, Documentation-Visibility
- landscape aspects and API lifecycle pillars, Landscape Aspects and API Lifecycle Pillars-Visibility
- of landscape of APIs, Managing the API Lifecycle in an Evolving Landscape-Summary
- security and, Security-Visibility
- strategy and, Strategy
- testing and, Testing-Volatility
- lifecycle, release, The API Release Lifecycle-The API Release Lifecycle
- LinkedIn, OKRs at, OKRs and KPIs
- load testing, What needs to be tested?
- logging, Visibility, Visibility
- loose coupling
M
- machine-driven governance, Governance Pattern #2: Machine-Driven Governance
- maintain stage of API product lifecycle, Stage 4: Maintain
- major versions, Versioning
- MAJOR.MINOR.PATCH pattern, Semantic versioning
- MAJOR.MINOR.PATCH.RELEASE pattern, Versioning
- mapping, of decisions (see decision mapping)
- marketing
- Maslow's hammer, Variety
- maturity
- maturity journey of API landscapes, API Landscape Journey-Summary, Variety-Variety
- McChrystal, Stanley
- McCord, Patty
- measurements
- microservices, Velocity
- minor versions, Versioning
- mock services, Velocity
- monitoring
- monitoring (API pillar), Monitoring-Key decisions for monitoring governance
- Morgan, Gareth
- mosaic of subcultures, Enabling Alexander’s Cultural Mosaic
O
- objectives and key results (OKRs), API usage tracking, OKRs and KPIs
- observability, monitoring and, Visibility
- onboarding (see customer onboarding)
- opportunity costs
- optimization, premature, API Landscape Journey
- organizational culture (see culture, organizational)
- organizational strategy (see strategy (API pillar))
P
- packaging, of deployments, Key decisions for deployment governance
- PageRank algorithm, Visibility
- parallels, testing and, Velocity
- patch versions, Versioning
- patterns, defined, Principles, Protocols, and Patterns
- PDF documents, API guidelines published as, Structuring Guidance in the API Landscape
- PDSA (Plan-Do-Study-Act) cycle, Incremental Improvement
- performance testing, What needs to be tested?
- personally identifiable information (PII), Vulnerability
- pillars, of API, The Ten Pillars of an API Product-Summary
- (see also as headings, e.g.: change management)
- change management, Change Management
- create stage and, Create-Security
- defined, More Than Just the API
- deployment, Deployment
- design, Design-Key decisions for design governance
- development, Development-Key decision for development governance
- discovery and promotion, Discovery and Promotion-Key decisions for discovery governance
- documentation, Documentation-Key decisions for documentation governance
- landscape aspects and, Landscape Aspects and API Lifecycle Pillars-Visibility
- maintain stage and, Maintain
- monitoring, Monitoring-Key decisions for monitoring governance
- product lifecycle and, Applying the Product Lifecycle to the Pillars-Change management
- publish stage and, Publish-Discovery
- retire stage and, Retire
- security, Security-Key decisions for security governance
- strategy, Strategy-Key decisions for strategy governance
- testing, Testing-Key decisions for testing governance
- Plan-Do-Study-Act (PDSA) cycle, Incremental Improvement
- platform principle, landscapes and, The Platform Principle
- PM (see product manager)
- policy-driven security implementation, Vulnerability
- Poppendieck, Tom and Mary
- popularity, discovery and, Discovery
- premature optimization, API Landscape Journey
- principled guidance, Governance
- principles
- process instructions, general principles vs., Governance
- product lifecycle, API, The API Product Lifecycle-Summary
- applying to pillars, Applying the Product Lifecycle to the Pillars-Change management
- create stage, Stage 1: Create
- defining an API objective, Defining an API Objective
- identifying measurable results, Identifying Measurable Results
- maintain stage, Stage 4: Maintain
- measurements and milestones, Measurements and Milestones-Identifying Measurable Results
- OKRs and KPIs, OKRs and KPIs
- publish stage, Stage 2: Publish-Milestones for the publish stage
- realize stage, Stage 3: Realize
- retire stage, Stage 5: Retire-Milestones for the retire stage
- stages of, The API Product Lifecycle-Milestones for the retire stage
- team roles in, Teams and API Maturity-Stage 5: Retire
- product manager (PM)
- production environment simulation, for testing, API testing tools
- production instance, API testing tools
- production testing, What needs to be tested?
- programming language choice (decision mapping example), Decision mapping example: Choosing a programming language
- promotion (API pillar), Discovery and Promotion-Key decisions for discovery governance
- proto-APIs, API Archaeology
- protocols, defined, Principles, Protocols, and Patterns
- publish stage of API product lifecycle, Stage 2: Publish-Milestones for the publish stage
R
- Randolph, Jason
- Ratzlaff, Cordell
- Raymond, Eric S.
- RDF (Resource Description Framework), Variety
- realize stage of API product lifecycle, Stage 3: Realize
- registries
- release
- release pipeline, Deployment
- Resource Description Framework (RDF), Variety
- results-oriented governance, Governing Decisions
- retire stage of API product lifecycle, Stage 5: Retire-Milestones for the retire stage
- return on investment (ROI), Volume
- reverse Conway, Recognizing Conway’s Law
- reversibility, Volatility
- risk reduction
- ROI (return on investment), Volume
- roles
- runtime discovery, Runtime discovery
S
- safety
- sandbox, API testing tools
- scale
- Schema.org, Vocabulary
- scope
- SDLC (system development lifecycle), The API Release Lifecycle
- search engines
- security (API pillar), Security-Key decisions for security governance, Security-Visibility
- security testing, What needs to be tested?
- semantic versioning, Semantic versioning
- service-oriented architecture (SOA), API Management at Scale
- Six Sigma, Variety
- Skok, David
- Smyte, Vulnerability
- SOA (service-oriented architecture), API Management at Scale
- SOAP (Simple Object Access Protocol), API Management at Scale
- Spectre, Rob
- speed
- spiral SDLC, The API Release Lifecycle
- Spotify, Teams and Roles at Spotify, Leveraging Dunbar’s Numbers
- squads, Teams and Roles at Spotify
- standardization
- state handling, Vulnerability
- strategy (API pillar), Strategy-Key decisions for strategy governance, Strategy
- Stripe, Customer Onboarding
- sublanguages, API Landscapes as Language Landscapes
- supporting assets, changing, Changing the Supporting Assets
- synthetic traffic, Velocity
- system development lifecycle (SDLC), The API Release Lifecycle
T
- tactics, for strategic API goals, Defining tactics
- Taleb, Nassim
- talent
- teach don't tell documentation method, Documentation methods
- teams, API Teams-Summary
- Alexander's cultural mosaic and, Enabling Alexander’s Cultural Mosaic-Enabling Alexander’s Cultural Mosaic
- API landscape management and, Teams
- API maturity and, Teams and API Maturity-Stage 5: Retire
- assembling during create stage, Stage 1: Create
- business roles, Business Roles
- Conway's law and, Recognizing Conway’s Law
- culture and, Culture and Teams-Supporting Experimentation
- Dunbar's numbers and, Leveraging Dunbar’s Numbers-Leveraging Dunbar’s Numbers
- experimentation fostered by, Supporting Experimentation
- roles for dealing with APIs, API Roles-Technical Roles
- roles vs. actual people on, API Teams-Scaling Your Teams on Paper
- scaling on paper, Scaling Your Teams on Paper
- scaling up, Scaling Up Your Teams
- Spotify model, Teams and Roles at Spotify
- technical roles, Technical Roles
- technical writers, Stage 2: Publish
- tell don't teach documentation method, Documentation methods
- ten pillars of API product (see pillars)
- test/QA (quality assurance) engineer, Technical Roles
- testing (API pillar), Testing-Key decisions for testing governance
- Thomke, Stefan
- Time to Wow! (TTW), Time to Wow!
- tool selection (decision mapping example), Decision mapping example: Tool selection
- tools
- Tran, Tai
- tribes, Teams and Roles at Spotify
- TTW (Time to Wow!), Time to Wow!
- Twilio, Onboarding for Your APIs
- Twitter, Vulnerability
- type 1/type 2 decisions, Scope of optimization
- type 1/type 2 deployment velocity, Velocity
V
- value, realizing (see realize stage of API product lifecycle)
- variety (landscape element), Variety
- antipatterns, Variety
- deployment and, Variety
- design and, Variety
- development and, Variety
- discovery and, Variety
- documentation and, Variety
- human systems and, Enabling Alexander’s Cultural Mosaic
- maturity and, Variety-Variety
- strategy and, Variety
- velocity and, Velocity
- velocity (landscape element), Velocity
- version control systems, API guidelines published in, Structuring Guidance in the API Landscape
- versioning (landscape element), Versioning-Semantic versioning
- viable business strategy, design thinking and, Viable Business Strategy
- virtualization
- virtualized services, Velocity
- visibility (landscape element), Visibility
- vocabulary (landscape element), Vocabulary-Vocabulary
- alignment of, API Landscapes
- change management and, Vocabulary
- concepts, Vocabulary
- defining, Vocabulary
- design and, Vocabulary
- enterprise information model and, Vocabulary
- management techniques for, Vocabulary
- maturity and, Vocabulary-Vocabulary
- of discovery, Vocabulary
- of documentation, Vocabulary
- visibility and, Visibility
- volatility (landscape element), Volatility
- volume (landscape element), Volume
- vulnerability (landscape element), Vulnerability
..................Content has been hidden....................
You can't read the all page of ebook, please click
here login for view all page.