Balance between System, Data and Operations
If even one of the legs
is in-correct, the stool
tends to topple
API,
Savvy?
Your web page, Sir
I canz do business
Separate Web and API interaction from the business logic
State A
State B
State C
Web Applications are “State-full”. Worry about “OOM”
Memory is a “scarce” resource
“State-full”
Vs.
Synchronous Asynchronous
Design and scale the synchronous aspects separately from the
asynchronous jobs – Not all operations need to be synchronous
Grid Database
Consider shipping copy of the data to Grid or dedicated
machines for batch or “secondary” tasks.
“Divide and Conquer”
Constantly monitor
the system for CPU,
Memory, Disk and I/O
Have system “raise”
events for critical
issues rather then
parsing log files.
Top Related