FaceQuest
Published in

FaceQuest

The role of AWS in building a SaaS product

In this post, I would give you sneak peak of the cloud components involved in building the product, FaceQuest, and some insights about the infrastructure

Overview of FaceQuest AWS Architecture

Functionality of part of the product hosted in AWS

FaceQuest — a face recognition service, the core functionlity is to —

  • detect the faces on the picture that is given to the API
  • accomplish the detection of faces, we would need some reference faces and hence the need to store the reference photos somewhere.

AWS components

Computation power to run the container

  1. While we could have used EC2, it often requires a great deal of tedious manual configuration and oversight. Managing these would require a great deal of resources and effort, and it takes time away from what’s most important: deploying applications.
  2. In order to spend minimal effort in managing the infra and to focus on the application itself we choose Fargate — serverless compute engine managed by AWS.

Advantages:

  1. Less complex — You don’t have to worry about where you’ll deploy your containers, or how you’ll manage and scale them. Instead, you can focus on defining the right parameters for your containers (e.g. compute, storage, and networking) for a successful deployment.
  2. Cost effective (I believe)— Fargate spot charges less than half the price Fargate usage would, by leveraging the spare compute capacity for the fault tolerant applications. By design, FaceQuest supports fault tolerant workloads.

Image Storage

Initially we decided to use Cloudinary as our image storage but upon analysis we found that it was not a right choice for our use case which involves lots of downloads from image storage service which would result result in spike in the costs. This would inturn require us to charge our customers obscenely. So we ended up using S3 as our image storage.

To learn more about this usecase and how we approached it visit here

Advantages:

  1. Cost effective — the costs were controlled because the worker processes downloading & processing the images run in AWS too
  2. Secure

If you would like to take a test drive of FaceQuest, the product that we are building, you can sign up for our Beta program.

--

--

--

Facial recognition as a Service

Recommended from Medium

How Would Wirth code?

A lightweight wrapper over Go’s HTTP client

If you have landed on this page means either you working with spring boot web flux trying to…

LeetCode 1225. Report Contiguous Dates

A tale of Continuous Integration and Deployment with Gitlab CI/CD at Grupo América

Event-Driven Architecture: Use Cases

The power of S.O.L.I.D design principles

The hidden costs of cloud

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Kamal

Kamal

More from Medium

How to win cloud and influence people

Adobe Experience Platform designed to co-exist with Multi-Cloud architecture

Build a Completely Serverless Machine Learning Demo on AWS

Serverless Data Engineering