2. Hello world
2
3rd year Azure MVP
+ 100Active
customers
2000 Belgium
2004 France
2008 Netherlands
2013 Portugal
2016 Switzerland
2016 U.K.
Close collaboration with Microsoft
+120 employees
Azure & IoT Advisor
8th year Microsoft P-TSP
Azure CAT support
Integration
Azure
IoT API mgmt
sam.vanhoutte@codit.eu
+32 474 849 993
@SamVanhoutte
be.linkedin.com/in/samvanhoutte
6. The interface is where the profit is
the world’s most popular media company creates no content
the most valuable retailer carries no stock
the world’s largest accommodation provider owns no property
the world largest taxi company owns no car
7. The story of the WiFi-Kettle
7
A British guys wanted
his morning tea.
8. The story of the WiFi-Kettle
8
Luckily he was a geek and decided to live tweet his 11hr struggle.
15. Chosing the right communication pattern
15
Information lookup
MostWeb API’s
Avoid data duplication
UI integration
RPC Async
Durable messaging
Scalable & multi-cast
Load leveling
Temporary unavailable
Bulk
Scheduled data exchange
Bulk or batch data
Traditional apps
Initial import & data load
16. Handle external communications
16
Requests outside of app
Security, monitoring
Documentation, portal
DNS handling
API
Management Queuing
Standards based
Durable messaging
Load leveling
Peek/lock/retry
Version
API versioning
Message versioning
Monitor usage
17. ➔ Testing is crucial
➔ Mostly scaling out is easier than scaling up
➔ Autoscaling is welcome, but complex
Resource sizes matter
17
Many small vs
Few large
The rise of
serverless
Autoscale &
test
18. ➔ Think about downstream (LOB?) systems
➔ Aggregate and forward, when possible
➔ Retries are important, but think about your strategy
Throttling will help your connected systems
18
Async
messaging Plan retries
Timers &
Reminders
19. ➔ Synchronization of cache & data store
➔ Think distributed
Cache, but not too much
19
Distributed
cache
Write through
Read behind
Stateful actors
or services
20. ➔ Use hashing algorithm, based on functional value
➔ Stateless vs stateful
Data & service partioning
20
Colocated data
Parallellism
over partitions
Partitioning
scheme
24. Fast iterations in the cloud
24
New services New features
Backwards
compatibility
Deprecation of
services
➔ Closely follow up on roadmap & announcements
➔ Design for change
➔ Use abstraction to cope with changes
➔ Foresee versioning or compatibility for externalAPI
Notas del editor
Multi tenancy
Tracing & logging
API management from the beginning
Scalability and partitioning
Security concerns
Pricing
Stateful vs stateless
Serverless
Scalability (small vs large)
Geo-deployments (traffic manager / cdn)
Concurrency & locking when scaling
Throttling
Businesses are seen as being innovative
IT is seen as catching up to innovation
3 components: proliferation of apps, data as management nightmare, smart devices that need to interact
Forrester report that surveyed 675 cloud developers
39% delivering an application integration solution
Higher than mobile, e-commerce
control the interface between the consumer and the provider
take a cut from the millions of consumers
Businesses are seen as being innovative
IT is seen as catching up to innovation
3 components: proliferation of apps, data as management nightmare, smart devices that need to interact
X API management from the beginning (external buffer)
X Scalability and partitioning
X Microservices - Stateful vs stateless
Serverless (attention points)
X Scalability (small vs large)
X Concurrency & locking when scaling
X Throttling
Businesses are seen as being innovative
IT is seen as catching up to innovation
3 components: proliferation of apps, data as management nightmare, smart devices that need to interact