Azure Application Architecture : Web-Queue-Worker

The center of a web-queue-worker architecture is based on the web front-end. The web front-end communicates with the worker using a messaging queue system. The worker is optional. If the application need to perform resource-intensive tasks, long-running workflows, or batch jobs then a worker is needed. Any long-running work is done asynchronously by the worker. The worker can be triggered by messages on the queue, or run on a schedule for batch processing. The front-end is implemented as an Azure App Services as well as the WebJob. Others components that […]

Read More →

Azure Application Architecture : N-tier

The n-tier (multi-tier) architecture is the traditional three-tier application separate with layers of services that has is own responsibility. It can be a logical or physical layers. The typical layers are the presentation (web), a middle tier (application/business) and the data layer (database). You can add any extra layers depending on the needs of the application or it could also be constituted with the presentation and data layer only.   When to use the n-tier architecture When you have a simple application to build When you want to migrate your […]

Read More →