CWIN17 India / gururaj joshi-micro services

Microservices platform for
delivering Commerce
Marketplace
Gururaj Joshi
Bangalore, September 27th
#CWIN17

Microservices platform for delivering Commerce Marketplace | 9/27/2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 2
Table of Contents
 Online Commerce Marketplace
 Changing Consumer Demands
 Solution Implementation Options
 Earlier Approach
 Why new ways of solution
 The Scale Cube
 Microservices
 Advantages of microservices
 Disadvantages of microservices
 Reference Stack
 Questions

Online Commerce Marketplace A place for great experience
the right way to build a brand is by delivering a great service.
“If you do build a great experience,
customers tell each other about that. Word
of mouth is very powerful”
Jeff Bezos
“All the aspects of trade & customer experience must work in harmony to
create an overall “brand experience” for the customer and this is what makes
people change their behavior and adopt new ways of purchasing”
Traditional Market Places
Online Market Places
….many more

Changing Consumer Demands
Today’s consumers demand to transact seamlessly anywhere, anytime, on any client.
Commerce is surviving
and thriving in today’s era
by creating experiences,
With the use of content
such as text, video, audio,
and so on.
Consumers no longer
see divisions between
channels (point of
sale, web, mobile,
kiosk, etc.)
A primary driver of
online shopping is the
additional functionality
that that it offers beyond
that of a physical store.
Every Internet-connected
consumer electronic device
hitting the market today offers
an interface that consumers
can use for shopping.
Consumers ask of
differentiation through
software is driving retailers
to build software from
scratch rather than buy it
prepackaged from a third-
party software vendor
A Brand Experience Consistency of
experience Across
Channels
Value-Added Features Convenience
Retailers turning into Software
Power house

Commerce Solution Implementation Options to Pick from
 Multiple features packages
 Continuous investment by vendor into new features
 Time to market slower than SaaS but significantly quicker than build
 Some prebuilt integrations may be in place for standard
PROS
 Cost is Consideration
 More features than actually required
 Monolithic solutions that may be difficult to adopt, may be hard to integrate
with existing IT systems
 Complex application to learn and manage
 Locked with vendor solution, difficult to switch if not satisfied
 Pace and freedom to innovate are limited
 May not fit your unique requirements
CONS
Buy
 Fast to market
 Lower upfront cost
 Easy to scale with demand
 Continuous enhancements/Upgrades standard features
PROS
 Success comes with cost (pay more for more traffic)
 Cannot innovate on your own pace
 Required Features may not be on roadmap
 Difficult to integrate with internal systems
 Full dependence on SaaS vendor
CONS
SaaS
 Build exactly to needs
 Take the full advantage of internal systems
 Be unique in market place, competitive advantage
 Fully leverage your previous investment in ERP and other internal systems
 More abilities with existing brick & mortal experience
 Build own IP
PROS
 Longer to implement than SaaS solution & Buy Solutions
 Requires knowledgeable Teams
 Initial cost is higher than SaaS & Buy
CONS
Build

Configuration & Settings
 Tax
 Payments
 Multi Currency
 Email Alerts
 Faceted Search
 Offline Checkout options
 Call for Actions
 Social networking
Catalog Management
 Category management
 Taxonomy
 Attributes and pickup values
 Variants and variations
 Form based listing tools
 Bulk listing tools
 Catalog Listing APIs
 Catalog connectors
Content
 Blog
 Product documents
 Product videos
 Product images
Promotions
 Cart promotions
 Catalog promotions
 Gift vouchers
 User promotions
 Discount vouchers
Pricing Engine
 Volume based prices
 Store based prices
 Customer segment based prices
 Promotion prices
 Customization based
Stores
 Store-based inventory, pricing, promotions,
products, freebies.
Delivery area mapping
 Store Operations
Store front Design
Themes
 Layouts
 Pages
 Custom CSS/JS
 Control Templates
 Containers
 Navigation
 Control and widgets
SEO
 Meta tags titles
 URL Masking
 Alt-text
 HTTP Redirect
 Heading tags
 Sitemap
 Google merchant center data feed
 Product micro formats and Rich snippets
 Web Analytics
Orders
 Order authorization
 Multiple dispatches
 Order queues by status
 Order Refunds & Returns
 Order Reports
 Log order conversation
 Delivery issues and tickets
 Import orders in bulk
 Order connectors for 3rd party properties
Typical Features of Market Place 1 of 2

Store front Experience
 Page
 Web parts
 Navigation
 Header Footer
 Template
 Theme
 Multilingual
 Form Control
 Call for Actions
Customer Activity
 Newsletter subscription
 Reward points
 Product rating
 Product reviews
 Discussions
 Social Updates
 Wish list / Shopping list
Cart & checkout
 Checkout
 Wallet
 Online payments
 Offline payments
 Lead capture
 Delivery mode
 Shipping charges
 Delivery slots
 EMI payments
Product discovery & search
 Category navigation
 Refine Search
 Text Search
 Product page
 Similar products
 Up sell products
 Recently viewed
 Recent searches
Customer Self-servicing
 Registration
 Login
 User group
 Order history
 Order tracking
 Invoices
Marketplace
 Product catalog
 Seller profiles
 Seller directory
 Commission management.
 Payment & Logistics
 Reports
 Marketplace campaigns
 Seller promotions
 Product QC
Marketing
 Landing pages
 Flash sales
 Banners
 Web Notifications
 RSS Feeds
 Mailing lists
 Campaign tracking
 Track cart abandonments
 Merchandizing and product tagging
Logistics and Shipping
 Shipping configuration
 Logistic partner setup
 Delivery zones and shipping speeds
 Delivery slots
 Shipment booking
 Shipment tracking
 Reverse logistics
Typical Features of Market Place 2 of 2

Most of earlier approach to build
Monolithic application
Almighty monolith was once believed with
its single database, in-process address
space, and thread per request model.
Modularity is achieved to various extents by
different modularization approaches but with
in same platform
Catalog Management
Stores Orders
Pricing Engine
Promotions
Content
Cart & checkout
Customer Self-servicing
Logistics & Shipping
Marketing
multi-million
lines of code
Time consuming
obstacle to continuous
deployment
conflicting resource
requirements
reliability.
difficult to adopt new
frameworks and languages
Customer Management
Payments
Registration
Administration
Monitor
simple to develop
simple to test
simple to deploy

Why new ways of solution
 Trade boundaries are shrinking and customer base is increasing
 Challenges in scaling up & large volume management
 Create systems that closely mimic how the world works
 Users want of experience across channels
 Users have come to expect millisecond response times (latency)
 Users want near to always uptime.
 Performance, that counts
 Protect users with a safe, reliable system
 Better and less complex code
 Looking for continuous innovation
 Adaption to newer and better frameworks

The Scale Cube
Y-axis - Functional Decomposition
Scale by splitting different things
•running multiple copies of an application with splitting
into multiple, different services. Each service is
responsible for one or more closely related functions.
Z-axis - Data Partitioning
Scale by splitting similar things
•running multiple copies of an application with each server is
responsible for only a subset of the data.
• Data is partitioned (a.k.a. sharded) across a set of servers
based on an attribute of each record.
Ref: The Art of Scalability by MARTIN L. ABBOTT & MICHAEL T. FISHER
3 dimensions to scaling consideration
X-axis - Horizontal Duplication
Scale by Clone
•running multiple copies of an application behind a load balancer.
•each copy potentially accesses all of the data

Microservices ……Way to go forward
The microservice architectural style is an approach to
developing a single application as a suite of small services,
each running in its own process and communicating with
lightweight mechanisms, often an HTTP resource API.
These services are built around business capabilities and
independently deployable by fully automated deployment
machinery.
Catalog
Management
Set of Simpler
Applications
Multiple Version
Each Service has
fixed responsibility
Faster Development
Cycles Automated continuous
& independent deployment
Specific resource
requirements
Polygot .
Different frameworks
and languages can be
adopted
API
Gateway
Orders
Management Payments
Promotions
Cart &
checkout
Pricing
Engine
MarketingLogistics &
ShippingRegistration
Notification
Web UI
Load balancing,
Access control,
API metering,
Caching, &
Monitoring
manageable chunks
or services.
scaled
independently
•complexity of distributed system
•handle partial failure
•partitioned database architecture
•eventual consistency-based approach
•carefully plan and coordinate the rollout of changes
•more moving parts that need to be configured, deployed, scaled, and monitored.
Other
System

Essential Traits of Microservice
Isolate All the Things
Act Autonomously
Single Responsibility
Own Your State, Exclusively
Stay Mobile, but Addressable
Self-Registration and Discovery Mechanism
Success depends on People & Process

API Gateway
microservice exposes a set of what are typically fine-grained endpoints
•makes separate requests.
•some might use protocols that are not web-friendly.
•might want to change how the system is partitioned into services by merging & splitting.
•Individual call makes client code much more complex
API Gateway
• Responsible for request routing, composition, and protocol translation.
• Serve requests by invoking multiple microservices and aggregating the results
• Load balancing, Access control, API metering, Caching, & Monitoring
• Translate between web protocols such as HTTP and WebSocket and web-unfriendly protocols that are used internally
•Mask failures in the backend services by returning cached or default data.
Zuul
Catalog
Management
API
Gateway
Orders
Management
Payments
Promotions
Cart &
checkout
Pricing
Engine
Marketing
Logistics &
Shipping
Registration
Notification

Service Discovery & Registry
client-side discovery
client is responsible for determining the network locations of available service instances and load balancing requests across them.
uses a load-balancing algorithm to select one of the available service instances and makes a request.
it couples the client with the service registry.
must implement client-side service discovery logic for each programming language and framework used by your service clients.
server-side discovery
The client makes a request to a service via a load balancer/ Proxy. Then it queries the service registry and routes each request to an available service instance
details of discovery are abstracted away from the client.
eliminates the need to implement discovery logic for each programming language and framework used by your service clients
the set of service instances changes dynamically because of auto scaling, failures, and upgrades. Consequently, client code needs to use a more
elaborate service discovery mechanism
Service Registry
The service registry is a key part of service discovery which is the database containing the network locations of service instances
Cart &
Checkout
Inst # 1
Router
Cart &
Checkout
Inst # 2
Cart &
checkout
Register
Service
Discovery
Registry
Service Registry
Update

Service deployment
need to run a certain number of instances of each service based on the demand for that service. Also, each service instance must be provided with the
appropriate CPU, memory, and I/O resources. What is even more challenging is that despite this complexity, deploying services must be fast, reliable and
cost-effective.
•Multiple Service Instances Per Host Pattern
•one or more physical or virtual hosts and run multiple service instances on each one
•Service Instance per Host Pattern
•run each service instance in isolation on its own host.
Orders
Management
Registration
Instance #1
Catelog
Orders Mgmt
Guest OS
Hypervisor
Host OS
Guest OS
Server Infra
Guest OS
CatelogRegistration
Service Instance per Container PatternService Instance per Virtual Machine Pattern
•Serverless Deployment
Orders Mgmt
Container Engine
Host OS
Server Infra
CatelogRegistration

strategies for refactoring ……..From Monolith to Microservices
Rebuild the application from scratch Build around old app & cut over to new services
(Strangler pattern)
Starting Position Early Days Nearly Finished Finished Position
OriginalMonolith
SetOfServices
OriginalMonolith
Finished Position
SetOfServices
Starting Position
One of the natural wonders are the huge strangler vines. They seed in
the upper branches of a fig tree and gradually work their way down the
tree until they root in the soil. Over many years they grow into fantastic
and beautiful shapes, meanwhile strangling and killing the tree that
was their host.
focus all of development efforts on building a new
microservices-based application from scratch.

CAP Theorem
( Brewer's theorem )
Consistency: every read would get you the most recent write
Availability: every node (if not failed) always executes queries
Partition-tolerance: even if the connections between nodes are down, the
other two (A & C) promises, are kept.
A
PC
Availability
Remains accessible and operational all time
Partition-tolerance
Only a total network failure can cause system to respond incorrectly
Consistency
Commits are atomic across
the entire distributed systems
Voldemort
CP
Can only choose 2 out of the 3
It is impossible for a distributed data store to simultaneously provide more than two out of the following three guarantees
Consistency, Availability, Partition-tolerance

Security Considerations
• Standard best practices for hardening
all of the servers, including using the
lowest privilege possible for services,
compartmentalizing functionality, and
removing all unnecessary services
• The Web server software and other
applications run in restricted
environments to prevent an attacker
from leveraging software flaws to gain
privileged access to the operating
system or critical services
Hardened
infrastructure
• The service designed to be stateless-
no session information is stored that
could be captured or compromised to
gain access .
• Designed to be compliant to security
guidelines such as Open Web
Application Security
Project (OWASP), CERT, SANS
Hardened
Applications
• Control access by specific users and
groups to specific content through a
Security Manager component
• Users authenticate with user IDs and
passwords, while system
administrators are required to use
strong authentication.
• Firewalls restrict access at the
network layer.
Access Controlled to
Servers
• Requiring SSL connections between
the client and the Web server ensures
confidentiality of data passed between
users and the portal.
• All administrative remote access to
the servers uses an encrypted secure
shell (SSH), and all files are encrypted
in transfer.
• Authorization standards such as
OAUTH 2.0 to be considered
• Input validation & Vulnerability
detection (XSS, CSRF, SQL Injection)
Secure
Communication by
Encryption
• Web security testing and remediation
• Day-to-day maintenance task of
tracking and evaluating bugs and
patches.
Security/
Vulnerability Testing
• Implement logging at multiple layers,
including network, operating system,
database, and application.
• Log data is captured and stored on a
secure host for processing and
retrieval.
• Real-time monitoring and incident
response with Intrusion detection and
log monitoring
• System availability is monitored at
several levels on a regular, automated
basis.
Auditing & Monitoring
• All the servers are backed up
regularly.
• The saved data is encrypted and
copied off-site for redundant storage.
• Consideration of regular drill of
backup and restore as part of
complete disaster response plan.
Backup and Recovery
• All system components are
considered to be redundant.
• Use of a load-balancer appliance
maintains availability of the Web
servers.
• Load balancing is for the application
servers, which provides the added
performance benefit of some degree
of caching
Redundant Systems

Advantages of microservices
Faster Time to Market
Faster time to market of new features is the most important benefit of microservices
True Omnichannel Commerce
Fully adopting microservices means having individual APIs that are the sole source of truth for granular business functions. The user interfaces on top of those APIs become
essentially
Better and Less Complex Code
Microservices tends to produce much better code because a single microservice performs exactly one business function & because a small team owns it and is responsible for it
Accountability
Each small team owns a single microservice from its inception to retirement.
Enhanced Domain Expertise
People are able to develop very deep domain-specific expertise because they look after just one small thing. For example, the business analyst responsible for promotions is going to
be the company’s expert on promotions.
Easier Outsourcing
It’s difficult to outsource roles such as development, operations, and QA with traditional monolithic applications because everything is so tightly coupled.
Security
Microservices is also better from a security standpoint because each microservice is independently deployed, often to its own private network within a public cloud.

Disadvantages of microservices
Outer Complexity Is More Difficult
Data synchronization, Security , Discovery , Versioning , Data staleness, Debugging
Organizational Maturity
Organizations must have a strong structure, culture, and technical competency.
Duplication
Products & instances form of part of duplication
Eventual Consistency
with microservices the fact is that not all data is strongly consistent
Data has never been consistent across an entire enterprise. For example, CRM, ERP, and commerce applications each have their own representation of a customer, with updates to
data being propagated between applications asynchronously.
Within a microservices-based commerce system, there is always at least one microservice that has the most up-to-date data. For example, the product microservice owns all product
data. But the product catalog and search microservices might have a cached copy of that data.
Testing
Integration testing in a remote environment becomes tougher with microservices. microservice’s functionality often requires writing test scripts that call other microservices to get them
to produce events that your microservice consumes.

Reference Microservices Platform for Commerse Marketplace
Micro Services
Landing Page Search Catalogs Cart Order Mgmt
Micro Services Micro Services
Why Micro Services based architecture
Notification Recommendations
Other Systems

Questions

Thank You!
Phone: +91 9590019491
Gururaj.Joshi@capgemini.com
Gururaj Joshi
Enterprise Architect
@mgururaji
Speaker 1
Photo

Appendix

www.capgemini.com
The information contained in this presentation is proprietary.
Copyright © 2017 Capgemini and Sogeti. All rights reserved.
Rightshore® is a trademark belonging to Capgemini.
www.sogeti.com
About Capgemini and Sogeti
With more than 180,000 people in over 40 countries, Capgemini is one of With more
than 190,000 people in over 40 countries, Capgemini is one of the world's foremost
providers of consulting, technology and outsourcing services. The Group reported
2016 global revenues of EUR 12.5 billion. Together with its clients, Capgemini
creates and delivers business, technology and digital solutions that fit their needs,
enabling them to achieve innovation and competitiveness. A deeply multicultural
organization, Capgemini has developed its own way of working, the Collaborative
Business Experience™, and draws on Rightshore®, its worldwide delivery model.
Sogeti is a leading provider of technology and software testing, specializing in
Application, Infrastructure and Engineering Services. Sogeti offers cutting-edge
solutions around Testing, Business Intelligence & Analytics, Mobile, Cloud and
Cyber Security. Sogeti brings together more than 23,000 professionals in 15
countries and has a strong local presence in over 100 locations in Europe, USA
and India. Sogeti is a wholly-owned subsidiary of Cap Gemini S.A., listed on the
Paris Stock Exchange.

CWIN17 India / gururaj joshi-micro services

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a CWIN17 India / gururaj joshi-micro services

Semelhante a CWIN17 India / gururaj joshi-micro services (20)

Mais de Capgemini

Mais de Capgemini (20)

Último

Último (20)

CWIN17 India / gururaj joshi-micro services