gool.li redesign
DESCRIPTION
The aim of the GOOL.li project is to develop a “Middleware” that can be used to access, search, sort, enrich, organize and present content , filtered by our vertical algorithms. IT strategies and orientations Scalability : Performance, Extensibility Flexibility : Ease of change Portability : Multiples devices, Mobility Interoperability : Standards et norms Reusability : Interfaces, integration Modularity : Components oriented User Oriented Services High Availability & Business Continuity : Clusters, Fault-tolerant … Loose coupling : Messaging, MVC … IT and architecture principals Our Architecture is based on WOA and ROA patterns (Rest/HTTP, Mashup….) 3 Layers : Business layer (PHP components), Edge layer (Template engine), Data layer (Data sources) PHP Web Workers Force to use CSI in place SSI Replace SQLDB by Key-Value system In-memory cache IT strategies and orientations Our Architecture is based on WOA and ROA patterns (Rest/HTTP, Mashup….) 3 Layers : Business layer (PHP components), Edge layer (Template engine), Data layer (Data sources) PHP Web Workers Force to use CSI in place SSI Replace SQLDB by Key-Value system In-memory cache Enterprise Integration patterns Conceptual architecture (As Is): Overview Our new architecture of “GOOL.li” is respecting the standards and the recommendations of SOA, ROA(REST) and WOA styles (*). Contribution : al akhawayn university, Ifrane, Morocco Jawad Jari Msc. Ing. Enterprise architect [email protected]TRANSCRIPT
ARCHITECTURE REDESIGN Master Project
Agenda
• Vision for GOOL.Li : Overview • IT and architecture principals • IT strategies and orientations • Conceptual architecture (As Is): Overview • Technology architecture (As Is): Overview • Technology architecture (To Be): Overview
Content Sources
GOOL.li
Vision for GOOL.Li : Overview
Access
Search
Filter
Enrich
Sort & Categorize
Present & Deliver
Medias
News
Web presence
Books & docs
Knowledge
Shopping
Mobile Apps
Cards
Customers HTTP HTTP
The aim of the GOOL.li project is to develop a “Middleware” that can be used to access, search, sort, enrich, organize
and present content , filtered by our vertical algorithms.
Assembly & Mashup
Reference : h1p://www.gool.li/why.php
IT and architecture principals
• Scalability : Performance, Extensibility • Flexibility : Ease of change • Portability : Multiples devices, Mobility • Interoperability : Standards et norms • Reusability : Interfaces, integration • Modularity : Components oriented • User Oriented Services • High Availability & Business Continuity : Clusters, Fault-
tolerant … • Loose coupling : Messaging, MVC …
IT strategies and orientations
• Our Architecture is based on WOA and ROA patterns (Rest/HTTP, Mashup….)
• 3 Layers : Business layer (PHP components), Edge layer (Template engine), Data layer (Data sources)
• PHP Web Workers • Force to use CSI in place SSI • Replace SQLDB by Key-Value system • In-memory cache • Enterprise Integration patterns
Conceptual architecture (As Is): Overview
Costumers (Services customers)
Services (providers)
Process
Components
Operational
Inte
grat
ion A
rchi
tect
ure
News Medias Knowledge Experts Mobile Apps Web presence
News Medias Knowledge Experts Mobile Apps Web presence
News
Wor
ker 1
W
orke
r 2
Wor
ker 3
W
orke
r 4
Medias Knowledge Experts Mobile Apps Web presence
Wor
ker 1
W
orke
r 2
Wor
ker 3
W
orke
r 4
Wor
ker 1
W
orke
r 2
Wor
ker 3
W
orke
r 4
Wor
ker 1
W
orke
r 2
Wor
ker 3
W
orke
r 4
Wor
ker 1
W
orke
r 2
Wor
ker 3
W
orke
r 4
Wor
ker 1
W
orke
r 2
Wor
ker 3
W
orke
r 4
Redis NoSQL
Message Bus
Virtual Server
Load Balancer
Our new architecture of “GOOL.li” is respecting the standards and the recommendations of SOA, ROA(REST) and WOA styles (*).
(*) h2p://www.ibm.com/developerworks/webservices/library/ws-‐soa-‐term1/
Technology architecture (As Is): Overview
Confidential
Technology architecture (To Be): Overview
Confidential
