OpenWhisk VS postman-app-support

Serverless functions are now offered by many cloud providers, as well as having options like OpenFaaS, Knative, Apache's Openwhisk and more from the open source community that run in environments ranging from one server all the way up to globally replicated private clusters.

OpenWhisk - https://openwhisk.apache.org

Example from: apache/openwhisk

The serverless functions with Digital Ocean are based on Apache Open Whisk, so the service has additional name space, which need to go into the URL.

The two biggest options are OpenWhisk and OpenFaas. Check out /r/serverless for more options. I'm experimenting currently with OpenFaas as it's the lighter weigh to of the two.

There are so many of them in big data, e.g. Kafka, Spark, Flink, Delta, Snowplow, Finagle, Deequ, CMAK, OpenWhisk, Snowflake, TheHive, TVM-VTA, etc.

The foundation is Apache OpenWhisk https://github.com/apache/openwhisk with DO specific customization to work with managed databased, log shipping, and other DO specific capabilities. The closest programming model is AWS Lambda in terms of the semantics and execution model.

Not necessarily an orchestrator, but you could take a look at https://openwhisk.apache.org/ it's like AWS Lambdas but for kubernetes (and open shift if you swing that way). Haven't used it personally, but the reading I've done on it suggests you could probably use it for this

cd openwhisk-deploy-kube helm repo add openwhisk https://openwhisk.apache.org/charts helm repo update helm install owdev openwhisk/openwhisk -n openwhisk --create-namespace -f /deploy/docker-macOS/mycluster.yaml

Do you have any details on the equivalent Postman change? How long ago did Postman force users to create an account? I found this github issue, but I'm not sure if it's what everyone keeps referencing.

https://github.com/postmanlabs/postman-app-support/issues/12...

As you can see, this solution worked as expected, but it still has a big concern. The idea of using user email and checking their permission will not prevent malicious people from using an admin email, which can be easy to get with social engineering, and use programs like Insominia or Postman to get the same response as an unprotected endpoint.

You have installed Postman.

Learned about curl https://curl.se/ and played around with postman https://www.postman.com/ some more.

Postman installed

The JWT authorizer is ready to use! We can use Postman or curl to test the endpoint and the authorizer.

Download POSTMAN from their official site https://www.postman.com/

In this tutorial, I will be using Visual Studio Code as the text editor and Postman for the HTTP requests, but feel free to use whichever tools you want.