Next2011 Architecture for the 10^x

Architecture for 10^X3d-scaling for real world problems

Donnerstag, 26. Mai 2011

Who we are

Markus Wolf, @KnisterPeterSenior Developer, SinnerSchrader

2

Meno Abels, @fastandfearlessDirector, SinnerSchrader


Architecture is important

Choosing an architecture has impact in several dimensions


Development


Operation


Maintaince

Maintenance


We want to sell our store-specific range of goods to our customers online

Customers should be able to collect these items within a appointed timeframe

In other words: “Click & Collect”

Sounds easy.

Our Briefing from


Wait: store-specific?


2*10^4 products4*10^2 shops (potential for up to 3*10^3)

... and adding:_unique prices and product-attributes per shop_subset catalogs for specific product lines

(e.g. Bio/Rewe-Feine-Welt/Angebote)_personalized catalog

We need to have as much webshops as real shops providing this service.

What else?


Personalized Catalog for each customer?


No standard shop software will meet these requirements

The Establishment will fail


We have a mission

Accept the challenge and think yourself


Use memory extensively=> around 10^6 faster than disks

Scaling in 1DHardware


Use parallel algorithms=> leverage multicore cpu



Use stateless components=> less error prone multithreading



Use view optimized Business Objects=> no transformation for view rendering



=> more requests per Server Instance (approx. 100 per second)



Scaling in 2DServer Instances



“Stateless Statefullness”_No server-side state_All state on client


Shared Nothing

„Kind of“ SOA

This means easy load-balancing=> weʼre cloud-ready!



Scaling in 3DClient Computer



Use client storage _Persist private data into browser_Caching of product data



Less server cycles_Gaining performance independent from server side_Green-IT


=> Less requests, faster user experience, happy users!



Scaling in RealitySimple Case


Enterprise toolchain


Future Proof


Server-Software lines of code <2*10^4 (common > 5*10^4)

Client-Software lines of code < 10^4(no one should need more)

Development Effort approx. (5*10^1) % (compared to traditional approach)

Deployment 3 Systems**Cost of operations per year is C.H.E.A.P.

Cost per user/year is roughly about:

The Result


The Result


Be careful!

Thank you.Donnerstag, 26. Mai 2011

Next2011 Architecture for the 10^x

Technology

Transcript of Next2011 Architecture for the 10^x