How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
The product serves as a function as a service, a serverless environment, you can say. It's a serverless environment, or, as some people call it, function as a service, FaaS. We have been using it as a mobile backend. We have a mobile frontend, a mobile application, which uses the AWS Lambda functions running in the cloud. It serves as an API backend for a mobile application that is running in the frontend.
It is useful in many scenarios. For example, in a microservices architecture where serverless functionality is required, one can use Lambda.
AWS Lambda has serverless programming, like Logic Apps from Azure. You just configure the run-time and then they start coding. It is event-driven. It started with my obtaining Salesforce. Salesforce is a low-code and non-code program and totally SAS. Everything starts from the event, from the trigger. You get the trigger and you work at the program. You have some other models, maybe faster or fancier models. But in my opinion, this kind of program is started by locating the system and identifying where the trigger and entry point of the program are. Then you get the full advantage of the program. You don't need to worry about any infrastructure. I think this is the future. Compared with the EC2, you don't have to pay anything if you don't run it. Otherwise, with EC2 when our client provisions the system and the instances, you always have to pay. There are other tremendous advantages, like flexibility. After you provision EC2 you can write something that does not totally follow the cloud convention. You use it to provision the container. With the program you need to have those 10 principles of cloud computing. Especially recently, within the past four or five years, I have gotten away from DevOps, or the software development life cycle. Even though I researched the product portfolio from DevOps and then the life cycle for DevOps, I try to position myself as an architect with hands-on experience. In my opinion, Lambda is very similar to Salesforce, which is the original for the SaaS platform and is an extremely low-code environment. With Microsoft and AWS you can say, "Okay. You can choose whatever language you need to make it even more flexible." Everything is the cloud. Lambda is a fully managed service. If you want to do it either as a private cloud or on-premise, I'm sure you can do that, too. But I don't know how to manage the pricing structure. But then you've lost the point of Lambda because if you do not use it, you do not pay. Again, I just want to emphasize, I'm not a Lambda expert. But, logically thinking, the big advantage of serverless programming for the customer is that you just use it and pay. Pay and go. You don't need to provision anything. All my experience with AWS Azure is on the public cloud. We do not get too deep. In IBM we do. When we do sales training we always get the private cloud on-premise. There are many reasons for this. One reason is that IBM lost the battle for the public cloud so we get into it much deeper. We go to the enterprise and we can deploy programs to your data center and offices. But for the tech data for AWS and Azure, we are all using the public cloud as a showcase when we talk to the customer and to the retailer.
We have some APIs and we use some mechanisms to process these APIs. Normally, some APIs need to be hosted by some servers. However, with this product, we can compute everything serverless.
We are a startup, and we are doing faster and cheaper storage for IT. We are going to offer our storage services in about two months, and we are starting with AWS. We do lossless compression using microservices. We do the compute in a lossless compression way similar to gzip, WinZip, or PKZIP, except that we are giving a discount to customers. The product that we are developing is not yet in the market. We are doing alpha testing for select customers who are using AWS. The biggest advantage is that you get faster storage without doing a forklift upgrade, and you get 35% cheaper storage. So, you get 2X faster storage with a 35% to 50% lower monthly bill. We use AWS Lambda to encode and decode data. I work on the encode and decode software. I am working with a cloud developer. He works on the Lambda deliverable and wraps my C code with his C++ wrappers. They get bundled together with no JS stuff.
Our primary use case is for our financial institutions. We use it for many customers that we work with. We develop solutions for our customers and run them on AWS. We wanted to build the solution on the public cloud and out of all the public cloud providers, AWS is the best. It has a rich set of services.
Primarily, I work with all my clients to provide them with solutions. We are a service company, so we work with clients to define and build applications that resolve their need for automation issues. I create the solutions, and then there is a delivery team of mine which works to deliver that solution to the client.
We have only used it for a few services. It's still in POC mode. We haven't done any production on it currently.
We use this solution for a mobile banking application with the ability to scale as per demand and to focus on core business functions rather than the platform.
Our primary use case for Lambda is for serverless computing in our project. We have an environment in AWS with Lambda, EC2, S3, SQS, RDS, and Redshift. Our Lambda function is triggered whenever a new object is put into S3. It will validate, extract data from S3 then input metadata into MySQL and put the main data into Redshift as the data warehouse. An SQS message will be created so our Application in EC2 is alerted that there is new data to have processed.
I back up my MongoDB, that database has user data. The performance of AWS Lambda has been fine.