sms-service | SMS library

I am new to Kubernetes. I created a server monitor and the selector select two services:

I have a very basic lambda function that get's invoked by AWS API Gateway and all the lambda does is just calls out to AWS SNS to send a text message. The lambda is versioned and configured with 1 provisioned concurrency with a status that reads "Ready"

I'm experiencing cold start latency of up to 13 seconds when invoking the versioned lambda for the first time after 20-30 minutes.

Below is the AWS API gateway log detailing how long it took to get a response back after invoking the versioned lambda with provisioned concurrency.

I am currently creating a program which automatically creates accounts on a Website and I want to verify them by SMS. I am using Python 3 and Selenium.

First the program to sends a request to the site.

I have a flask app, that i want to dockerize, so i have used the following Dockerfile

I'm implementing an SMS service in a loopback4 application. I have my service class which has one method, but when I try calling it in a controller endpoint, after injecting the dependency and binding the service to the application, I get an error that says that it is not a function although typescript asks me for the 2 parameters that it requires, how can I fix this?

This is the service class

I'm working on SMS-Gateway that holds multiple charged SMS-services with different numbers,
each SMS sent to the customer has 4 status as below (forwarded, delivered, expired,delivery failed)

Now I have the below first_table for the charging-system with the below details (TABLE-A)

and below (TABLE-B) which contain the status of each sent SMS with its ID

Below is my expected final result to forecast the details for each sms-service :

At first I thought it was easy all I need is just to use COUNT(Case when ...)
but in my case I have thousands of SMS-numbers(services) so if I use this approach it will be like that:-

I'm building a application with microservices architecture.

So basically, my app look like this

I have configured and connected an SMSC to receive SMS on Kannel properly. I am able to receive SMS successfully, as I can see from access logs, but not getting hit on my API.

This is the configuration file :

Scenario:

This is my login scenario for my microservice application:

1. The user enters his phone number
2. A verification code will be sent
3. The user must send the received code to verify it
4. The user must enter his password
5. A JWT Token will be received

REST Implementation

For implementing the given scenario, I've created three services: auth, sms, and user. From my point of view, I think it's better to handle requests for sending verification code and generating JWT token from user-service. Here is the detail of my implementation:

• User calls POST /user/sms to send his phone number to the user-service. Inside that, a request will be made to the sms-service to send the verification code.

• Then user calls POST /user/verify to verify the code, again this request will be handled inside the user-service. If the code is valid, user-service will generate a temporary token and pass it to the header response (assume that the user is already registered into the system)

• Now the user passes his password with the temporary token via POST /user/password. If the credentials are valid, user-service will call auth-service to get a JWT token and append it to the response header of POST /user/password.

Question

Are there right communications between user<->auth and user<->sms services?