Suppose you have a web site consisting of:
- A web server serving your various users requests
- A DB for persistence
- A separate server asynchronously doing background stuff – preparing the data on the DB, updating it according to changes, etc. – regardless of what’s going on in the main server.
You can easily translate this into another world and talk about threads for example – i.e. having one thread preparing the data asynchronously for a main thread which is running.
Is there a name for this pattern, if it is a pattern at all?
Are there any pros/cons for this method of processing data in terms of performance?
Let me just clarify that I’m asking specifically about the second web server doing background processing, and not the whole architecture.
Everything has patterns. If you’ve seen it more than twice, there’s a pattern.
You’ve got three examples of Client-Server.
You’ve got Browser-Web Server.
You’ve got web server in the role of DB Client talking to DB Server.
You’ve got web server in the role of App server client talking to an App Server.
Sometimes folks like to call this N-Tier since there are at three tiers of Browser-Web Server-DB Server, plus an additional application server tier.
Some folks expand this into the Services Bus concept. Your web server uses DB server and application server.
The Asynchronous Back-End and Back-end Server are names I’ve heard to describe your application server architecture.