eCommerce Series Part 5 - Enterprise Architecture
3 likes•716 views
This document discusses ecommerce architecture and outlines approaches for omni-channel architecture, decoupling client and server sides, and session management. It describes moving from tightly coupled to decoupled systems and integrated to API-based. It also discusses serving static content from the cloud and rest from data centers, decoupling the UI and backend using SSL/TLS or caching, and storing sessions on the client, web tier, server side, or in a hybrid approach.
eCommerce Series Part 5 - Enterprise Architecture
- 1. Ashwinee Kumar Nov 2015 Ecommerce Architecture Ecommerce Series – Part 5
- 2. 2 Agenda 1. Ecommerce architecture 1. Omni channel 2. Client and server side 3. Session management
- 4. Omni channel architecture 4 • Tightly Coupled to Decoupled • Multiple data source to single • Integrated heterogeneous system to API based • Channel specific customer experience to Seamless unified experience
- 5. Decouple client side from server side 5 Serve static content from cloud rest from data Center • Better client side performance • Differing requirements – Security, availability, reliability • Unified view across channels – eg. shopping cart, user profiles, simultaneous access to account
- 6. Approaches to Decouple UI and Backend 6 1. To secure client-backend interaction use SSL/TLS, VPN, dedicated fiber line 2. To reduce latency between client-backed use WAN accelerator, GLSB b/w client and backed with latency based routing Hybrid: Cloud based UI and DC based backend
- 7. Approaches within Cloud based decouple 7 Caching Entire Pages 1. Serving static pages from your frontend in the cloud, going back to backend as required 2. Reaching the backend can be optimized further by caching backed output in the cloud based on keys from certain factors (customer logged in, geo location, user agent, locale). Few Proxies and LB have this capability Overlaying HTML on Cached Pages 1. In the case of partly static pages, static content can be cached. Dynamic content can be fetched asynchronously (ajax) as the page loads on client Using CDNs to insert HTML 1. In the case of partly static pages, static content can be cached. Dynamic content can be fetched (esi) in cdn before rendering on client. 2. Advantage: Client need not know JavaScript, UI and backend can be one monolithic
- 8. Approaches within Hybrid-cloud based decouple 8 Overlaying HTML on the Server Side 1. Serving your frontend independently of your backend 2. Pulling in only small, dynamic fragments from backend 3. Frontend is then free to run wherever you want Everything but the Database in the Cloud 1. Requires direct connection between cloud and DB for better performance Fully decoupled front end and backend 1. Response from the backend should be XML or JSON (raw data) instead of HTML 2. Easier to deliver your solution to non browser clients such as mobile
- 9. Session Management 9 1. Definition of Session (state) – Relevant information during customer interaction with a web application. Eg.. Content of shopping cart 2. Where can it be stored – Client, Web tier, Server side, Hybrid 1. Client – security concern, limited storage 2. Web tier – easy to implement, but user is locked to web tier node, due to stickiness utilization of nodes is not possible when a new node is added 3. Server side – NoSQL or Cache, most optimal 4. Service, Data tier – They do not store states as they are meant to be stateless