apidays LIVE India 2022: Accelerating India’s digitisation with APIs
May 11 & 12, 2022
Breaking boundaries of the Old Giant – ERP Intelligently Integrated
Garima Srivastava, Chief Development Architect at SAP Labs
------------
Check out our conferences at https://www.apidays.global/
Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8
Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io
Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/
Deep dive into the API industry with our reports:
https://www.apidays.global/industry-reports/
Subscribe to our global newsletter:
https://apidays.typeform.com/to/i1MPEW
2. 2022 SERIES OF EVENTS
New York
JULY
(HYBRID)
Australia
SEPTEMBER
(HYBRID)
Singapore
APRIL
(VIRTUAL)
Helsinki & North
MARCH
(VIRTUAL)
Paris
DECEMBER
(HYBRID)
London
OCTOBER
(HYBRID)
Hong Kong
AUGUST
(VIRTUAL)
JUNE (VIRTUAL)
India
MAY
(VIRTUAL)
APRIL (VIRTUAL)
Dubai & Middle East
JUNE
(VIRTUAL)
Check out our API Conferences
www.apidays.global
Want to talk at one of our conferences?
apidays.typeform.com/to/ILJeAaV8
3. Garima Srivastava
Chief Product Development Architect at SAP Labs India Pvt. Ltd
with more than 16 years of Software development experience in various
domains like Enterprise Development, Cloud Computing, Microservices
Development, Integration Across Platforms, Enterprise Software Enablement on
Cloud, Enterprise Mobile Application Development.
About Me
6. How can APIs Help
Smooth Integration between multiple
enterprise applications across deployment
offerings
Seamless Integration
Ease of new developments , connect to best-of-
breed solutions efficiently,
Provide flexibility to make connections with
new business partners, offer new services to
their existing market, and, ultimately, access
new markets
B2B collaboration
Faster Product & Service innovation
Improved Collaboration
APIs allow businesses to share the business
relevant data offered by another business.
Paving the path to Public Cloud Journey
Businesses targeting cloud adoption embrace API based Integration patterns to
create well defined modularized development artefacts.
7. High Level Considerations for API
Strategy
Product Features
•Offer features and functionality that business applications need
Release & Utilization
•Control the API's release and future development
Performance
• Consider the performance of the APIs while designing
the E2E Integration use cases
Security & Monitoring
•Adequate authorization, authentication, Monitoring & Logging to
safe-guard business data
8. Empowers leak detection to move from reactive
to proactive business intelligence
Mediated Integration or process integration
platforms allow to integrate various business
processes
Exposure of API on Cloud
Usage of an Integration Platform
Providing a well-organized API hub/cockpit
where APIs can be documented for efficient
identification
Identification of the API
Key Pointers for Hybrid Integration
Precise Definition of APIs
End to end Integration via defining right set of
APIs in the system landscape.
Efficient extension of APIs
Extending APIs for business or functional usages
by internal, customer or partner teams
9. API Types to Consider
Open APIs
• open source and access
with the HTTP protocol
• ’public APIs’
Partner APIs
• exposed to or by
business partners
• credentials required to
access partner hosted
APIs
Internal APIs
• not exposed to external
users.
• Used for increasing
development efficiency
within the org
Composite APIs
• combination of multiple
data or service APIs
• useful in microservices
architecture
10. Common Protocol Specification considered
for Hybrid Integration
Simple Object Access Protocol
SOAP
• intended to be extensible, neutral (able to operate over a range of communication protocols,
including HTTP, SMTP, TCP etc.), and independent (it allows for any programming style)
Representational State Transfer Architecture
REST
• uses client-server architecture, cacheability, adheres by the rules of statelessness, works well with
a layered system design, uniform interface.
• OData( Open Data Protocol) can be a preferred option.
11. API Management Platform & API Gateway
Enables easy discovery and connect to the APIs that can be consumed within/outside
the organization
Should provide catalogue of APIs with accurate documentation for ease of usage
Useful for version control, API distribution, enabling partner to publish related
APIs, Tool integration for a plethora of APIs within an organization
Gateway sits between a client and a collection of backend services, handle tasks that
like user authentication, rate limiting, and statistics.
12. Mediated Integration vs Direct Integration
Mediated Integration
• Unaligned APIs
• Middleware Content required to do
Direct Integration
• Aligned Business Contexts & API
• No need of a middleware for
13. Aligned Business Context for API
Design
Business Context Alignment
• Agreement on business domain and its characteristic to be opened in API
• Common representation of aligned context