The Backend App currently offers a Content API for generating raw data for assets. To further assist MXD users, it is essential to provide a method for pre-seeding various payload sizes.
This service is needed because the current setup requires users to interact with two separate endpoints: one for generating random content and another for creating content. Users must first generate the data and then create the content. The new endpoint generates and creates content simultaneously, which is more efficient.
Supporting different payload sizes is needed for performance testing. Generating content with different payload sizes will help identify potential performance bottlenecks.
Description
The Backend App currently offers a Content API for generating raw data for assets. To further assist MXD users, it is essential to provide a method for pre-seeding various payload sizes.
This service is needed because the current setup requires users to interact with two separate endpoints: one for generating random content and another for creating content. Users must first generate the data and then create the content. The new endpoint generates and creates content simultaneously, which is more efficient.
Supporting different payload sizes is needed for performance testing. Generating content with different payload sizes will help identify potential performance bottlenecks.