A method of scaling an application based on application scenarios (410, 420, 430) representing portions of the functionality of the application, implemented by at least one computing device, the method comprising: in a database server system, receiving a request (140, 340, 620) to execute a logic asset, wherein the database server system comprises: a database master node (120, 320) storing resource content comprising one or more tables (122, 124, 326, 327, 328) and one or more logic assets associated with the application, and multiple application scenario nodes (130, 335) storing replicas (132, 336, 337, 338) of the resource content comprising data from a subset of the one or more tables (122, 124, 326, 327, 328) and a subset of the one or more logic assets associated with an application scenario, wherein the data from the subset of the one or more tables (122, 124, 326, 327, 328) and the subset of the one or more logic assets are associated with the application scenario (410, 420, 430) by a stored application scenario configuration that specifies how many of the multiple application scenario nodes (130, 335) store the replicas (132, 336, 337, 338) of the resource content associated with the application scenario (410, 420, 430); determining that the request (140, 340, 620) is associated with the application scenario (410, 420, 430); and processing the request (140, 340, 620) on one or more of the application scenario nodes (130, 335), wherein processing the request (140, 340, 620) comprises accessing the replicas (132, 336, 337, 338) of data from the subset of the one or more tables (122, 124, 326, 327, 328) stored on the one or more application scenario nodes (130, 335); wherein the data from the subset of the one or more tables (122, 124, 326, 327, 328) is selected based on a filter criteria associated with the application scenario (410, 420, 430). in a database server system, receiving a request (140, 340, 620) to execute a logic asset, wherein the database server system comprises: a database master node (120, 320) storing resource content comprising one or more tables (122, 124, 326, 327, 328) and one or more logic assets associated with the application, and multiple application scenario nodes (130, 335) storing replicas (132, 336, 337, 338) of the resource content comprising data from a subset of the one or more tables (122, 124, 326, 327, 328) and a subset of the one or more logic assets associated with an application scenario, wherein the data from the subset of the one or more tables (122, 124, 326, 327, 328) and the subset of the one or more logic assets are associated with the application scenario (410, 420, 430) by a stored application scenario configuration that specifies how many of the multiple application scenario nodes (130, 335) store the replicas (132, 336, 337, 338) of the resource content associated with the application scenario (410, 420, 430); a database master node (120, 320) storing resource content comprising one or more tables (122, 124, 326, 327, 328) and one or more logic assets associated with the application, and multiple application scenario nodes (130, 335) storing replicas (132, 336, 337, 338) of the resource content comprising data from a subset of the one or more tables (122, 124, 326, 327, 328) and a subset of the one or more logic assets associated with an application scenario, wherein the data from the subset of the one or more tables (122, 124, 326, 327, 328) and the subset of the one or more logic assets are associated with the application scenario (410, 420, 430) by a stored application scenario configuration that specifies how many of the multiple application scenario nodes (130, 335) store the replicas (132, 336, 337, 338) of the resource content associated with the application scenario (410, 420, 430); determining that the request (140, 340, 620) is associated with the application scenario (410, 420, 430); and processing the request (140, 340, 620) on one or more of the application scenario nodes (130, 335), wherein processing the request (140, 340, 620) comprises accessing the replicas (132, 336, 337, 338) of data from the subset of the one or more tables (122, 124, 326, 327, 328) stored on the one or more application scenario nodes (130, 335); wherein the data from the subset of the one or more tables (122, 124, 326, 327, 328) is selected based on a filter criteria associated with the application scenario (410, 420, 430).