How would I go about creating an app like "Lensa" with Stable Diffusion?

1

Amazon S3

My guess of how Lensa works on the backend, which might be a suitable thing to mimic are; - User uploads their images via the app to the cloud, likely to an AWS S3 cloud storage repository. - When the user's images are uploaded, it triggers a serverless function, likely running on AWS Lambda, that provides the path to the user's uploaded photos, and some metadata about the user (probably their name, or a unique identifier), to a Load Balancer, which handles the high volume of users using Lensa, and basically "queues" the user for their images to be processed. - When a server frees up (I'm guessing Lensa has a bunch of AWS EC2 servers that they're "renting," likely higher-end with good graphics cards), the user's photos are passed into that server, which runs a script and does "Dreambooth." With ten or twelve photos, and a powerful enough server, this is probably running Dreambooth in about ten minutes, and when the Dreambooth process completes, it generates a new, customized-for that-user, Stable Diffusion model, in which the new model is probably then stored back on AWS S3. - Once the model is saved, that server likely runs a script to use this custom Stable Diffusion model and provides it with 10-100 random prompts, which generates a bunch of images.

#Cloud Hosting #Object Storage #Cloud Storage 170 social mentions

2

AWS Lambda

My guess of how Lensa works on the backend, which might be a suitable thing to mimic are; - User uploads their images via the app to the cloud, likely to an AWS S3 cloud storage repository. - When the user's images are uploaded, it triggers a serverless function, likely running on AWS Lambda, that provides the path to the user's uploaded photos, and some metadata about the user (probably their name, or a unique identifier), to a Load Balancer, which handles the high volume of users using Lensa, and basically "queues" the user for their images to be processed. - When a server frees up (I'm guessing Lensa has a bunch of AWS EC2 servers that they're "renting," likely higher-end with good graphics cards), the user's photos are passed into that server, which runs a script and does "Dreambooth." With ten or twelve photos, and a powerful enough server, this is probably running Dreambooth in about ten minutes, and when the Dreambooth process completes, it generates a new, customized-for that-user, Stable Diffusion model, in which the new model is probably then stored back on AWS S3. - Once the model is saved, that server likely runs a script to use this custom Stable Diffusion model and provides it with 10-100 random prompts, which generates a bunch of images.

#Cloud Computing #Cloud Hosting #Backend As A Service 244 social mentions

3

AWS Elastic Load Balancing

My guess of how Lensa works on the backend, which might be a suitable thing to mimic are; - User uploads their images via the app to the cloud, likely to an AWS S3 cloud storage repository. - When the user's images are uploaded, it triggers a serverless function, likely running on AWS Lambda, that provides the path to the user's uploaded photos, and some metadata about the user (probably their name, or a unique identifier), to a Load Balancer, which handles the high volume of users using Lensa, and basically "queues" the user for their images to be processed. - When a server frees up (I'm guessing Lensa has a bunch of AWS EC2 servers that they're "renting," likely higher-end with good graphics cards), the user's photos are passed into that server, which runs a script and does "Dreambooth." With ten or twelve photos, and a powerful enough server, this is probably running Dreambooth in about ten minutes, and when the Dreambooth process completes, it generates a new, customized-for that-user, Stable Diffusion model, in which the new model is probably then stored back on AWS S3. - Once the model is saved, that server likely runs a script to use this custom Stable Diffusion model and provides it with 10-100 random prompts, which generates a bunch of images.

#Web Servers #Web And Application Servers #Load Balancer / Reverse Proxy 22 social mentions

4

Amazon EC2

My guess of how Lensa works on the backend, which might be a suitable thing to mimic are; - User uploads their images via the app to the cloud, likely to an AWS S3 cloud storage repository. - When the user's images are uploaded, it triggers a serverless function, likely running on AWS Lambda, that provides the path to the user's uploaded photos, and some metadata about the user (probably their name, or a unique identifier), to a Load Balancer, which handles the high volume of users using Lensa, and basically "queues" the user for their images to be processed. - When a server frees up (I'm guessing Lensa has a bunch of AWS EC2 servers that they're "renting," likely higher-end with good graphics cards), the user's photos are passed into that server, which runs a script and does "Dreambooth." With ten or twelve photos, and a powerful enough server, this is probably running Dreambooth in about ten minutes, and when the Dreambooth process completes, it generates a new, customized-for that-user, Stable Diffusion model, in which the new model is probably then stored back on AWS S3. - Once the model is saved, that server likely runs a script to use this custom Stable Diffusion model and provides it with 10-100 random prompts, which generates a bunch of images.

#Cloud Computing #Cloud Infrastructure #VPS 62 social mentions