We have just started with Lambda and it is great.

We did not use another solution prior to AWS Lambda.

I don't actually use AWS Lambda. I'm a distributor. I try to explain solutions to the vendor. I previously used Salesforce Apex. I use the Azure Logic App service.

Salesforce does not have so many options to choose from, such as Java or C++. Salesforce said, lets invent a language. They call it "invent" but actually they just made a simplified edition of Java and eliminated a lot of complex features. Now all the syntax is the same. Salesforce is a business company. They focus on business solutions development and they make the customer's lifecycle development simple. AWS really does not stick to any business because they are a technology company.

Let me explain the similar things that Lambda has to Salesforce. When you get the event you have to see our form. With the sales approval process, if you have the 50% to get to the half million and above, you need the vice president to get the approval. You can use this trigger based serverless program. All you want to do is to write down the logic and then put it under the trigger of whenever a certain number changes in the half billion, and then you need to do the multiple steps.

This kind of programming is easily defined in the business. All you need to do is get the logic done, get it tested, see the steps you are doing, and then fix up the errors. As for Lambda, as I said, I've just experienced two very simple examples in the AWS, but they were the same thing.

Logic App and Lambda should be doing the same thing - fully managed coding. You focus on the logic triggered by the certain events. And there are other additions within the Lambda family. It can be scheduled as a batch job. I don't think it's originally lack of motivation from the serverless. The serverless is from the trigger.

One of the reasons my company went with AWS Lambda is that it's serverless, so you don't need to manage any server because AWS will handle it. This means that a lot of responsibilities will be taken care of by AWS, which helps you avoid many problems.

Another reason for choosing AWS Lambda is its stability. Latency is also not a problem on AWS Lambda, allowing you to use different services in your AWS account securely. For example, when you want to reach the AWS billing service, you can do it within the environment of your AWS account without an external tool, which makes it very secure. AWS Lambda also helps you reach other AWS accounts securely because it depends on roles rather than search keys or passwords.

We previously used Azure and Volvo

Azure Logic App & Function App, Google Pub-Sub etc. 

We didn't use a different solution apart from AWS Lambda.

Before implementing Lambda, we had legacy types of solutions. 

While something was used before, it likely wasn't serverless. 

I'm aware that Oracle and Azure have certain options available.

I didn't use a different solution before implementing Lambda. 

I have not used other solutions prior to AWS Lambda.

We use a number of AWS services.

I saw Ops setup the automated release jobs faster in AWS than in Jenkins and CircleCI.