According to a report published by Temando, 78% of consumers want same-day shipping, 86% of consumers have used or would like timeslot deliveries, 89% of consumers expect to see multiple shipping options at the checkout and 96% of consumers want the visibility to track their deliveries online, but only 65% of retailers are offering it. Shipping and fulfilment is now in the limelight! Customer demand for choice and mobility is increasing exponentially having become a key differentiator for competitive advantage. Based on these stats, convenience is key. CitySprint On the dot’s new product is set on a path to disrupt the timed delivery space and deliver the convenience consumers require.

1. Digital Transforma/on Journey
On the dot
Deliveries when you want them !
Eduard Lazar
Sr. Solu/on Architect
LastMileLink Technologies , a CitySprint Innova/on Lab

2. Market Survey
• 78% of consumers want same day shipping
• 86% of consumers have used or would like
;meslot deliveries
• 89% of consumers expect to see mul;ple shipping
op;ons at the checkout
• 96% of consumers want the visibility to track their
deliveries online
• 65% of retailers are offering it.
Source : Temando

3. Digital Transforma/on Journey
Posi2vely Disrupt the Timed Delivery Space
By building a Cloud Native Platform, an eco-system
exposing business features as APIs enabling new
channels for customer engagement and revenue
growth.

4. Key Challenges
• Move to Cloud
• Create Open RESTful APIs
• Enable Iden/ty Federa/on
• Foster innova/on by crea/ng a Developers
Community
• Simplify Integra/on
• Create a successful Cloud Na/ve PlaMorm

5. Why WSO2?
Various platforms were evaluated based on the following tenets:
Capability
vs.
Requirement
matrix
Formats &
Protocols
Connectors
Design & run
Time
Governance
Java/J2EE
Resource
availability
Cloud vision
Support &
Documenta-
tion

6. WSO2 Selected Components for our Platform
API Manager + ESB
• API Manager -publish,
subscribe, collaborate
• Workflow for signup -
Sandbox & Produc/on
• (Micro) Services-based
architecture
• ESB – support
transforma/on &
orchestra/on
DevOps
• AWS based deployment
• Mul/ zone & region
availability
• High speed Cassandra
NoSQL database
• DevOps to manage the
scale
Iden2ty Server
• Support for SAML, OAuth,
JWT – Federated Iden/ty
• XACML & RBAC
Authoriza/on
• Mul/-tenancy

7. Birdseye View Architecture

8. Con/nuous Deployment with WSO2
AWS CFT

9. WSO2 (New World) vs. TIBCO (Old World)

10. Our PlaMorm Goal
To spark Interac2on between Producers and Consumers which
generates value for all plaGorm users
• On the dot offers Retailers a convenient fulfilment
method
• On the dot offers Consumers a:
– Convenient delivery /me slots
– Convenient collec/on /me slots
• On the dot offers an API ecosystem to drive Innova/on
via a Developers Community and ease of integra/on

12. At the heart – Open APIs
APIs
.
.
. .
.
• API Economy
– Reach, Community
– Engineering
– Innova/on
– Integra/on
– Revenue
Reach
Revenue Proven
tech
Innova/on Integra/on

13. APIs Evolu/on landscape
1st Tier
• Monolith
2nd Tier
• Client/Server - PCs
3rd Tier
• Web Applica/ons , N /er
.
• Many APIs, Faster Itera/on , Looser Coupling, Integra/on is priority
4th Tier
• Mobile APPs, APIs and Cloud Na/ve PlaMorms

14. Top 5 reason a plaMorm can make sense
Lifecycle
Integra/on
Skillsets
Speed COST

15. Cloud Na/ve PlaMorm considera/ons
• Cost – does it control cost through
simplifica/on and reuse?
• Speed – is it saving /me or just
work?
• Skillset – will I need fewer or more,
is it future-proof ?
• Integra2on – will it save /me and
complexity?
• Lifecycle – does it model the en/re
lifecycle, or just pieces of it ?
More Complexity = More Time

16. #1: Cost
The short-term investment in
crea/ng those first apps is likely
to be the /p of the iceberg in
terms of people and capital
costs.

17. How cost mount…
Business Users Technology Churn Devices & OSes IoT

18. #2: Speed

19. Speed is great but challenging as ever …
Client
PlaMorms
Data Silos Integra/ons
Skill
Shortage
Change
Frequency &
Upgrade Path

20. #3: Skillsets
Specializa/on is for insects – Robert A. Heinlein

21. Exper/se needed
• Sokware stacks are growing unwieldy
• One API/App can touch dozens systems – or more
• Time lost to ramp-up is a “silent killer”
• Language du jour and Framework du jour issues

22. #4: Integra/on
On
the
dot

23. Integra/on
• Integra/ons are not difficult but they are a
HUGE and recurring Time Drain hipng the
boqom line
• Average # of APIs in cloud service is @ 400
x 10’s – 100’s of APIs in today's enterprise
• With the transi/on from 3rd to 4th /er –
their number increases, the have to be
loosely coupled and as such integra/on is
a priority

24. Focus on Microservices Architecture
• Services exposed and consumed via REST and SOAP
• Good News – Everything is ready to use
• Bad News – We s/ll need to wire it all together
– Standardiza/on in protocols
– Not in the implementa/on of the services
• Requires Enterprise Architect oversight
– APPs have much in common , simplify and re-use
where possible

25. #5: Lifecycle
• Con/nuous Delivery ( and integra/on )
• Agility is all about itera/on
• Interdependencies X # of APIs = Poten/al point of failure
• No more Silos of Dev and Ops
• API Versioning
Design Develop Test Deploy Manage Repeat

26. Customers &
Partners
(External)
Result – On the Dot Cloud Na/ve PlaMorm !
Connected
Devices
Connected Data
Connected
Platforms
Connected UX
Enterprise
(Internal)
API-centric SOA
Big Data/
Complex Event
Processing
Agile Delivery and
DevOps
Mobile First/
Cloud First
On the
dot
Collabora2ve
Adap2ve
Integrated
Accessible

27. Fast forward a few years from now …
On the dot daily orders loca/ons

28. Thank You!
#WSO2ConEU
Share your feedback for this session
wso2con.com/app