AWS Lambda vs IBM Cloud Foundry

• AWS Lambda is a welcoming platform, supporting several languages, including Java, Go, PowerShell, Node.js, C#, Python, and Ruby. And if you need to deploy a Lambda function in another language, AWS offers a Runtime API for integration.
• We really appreciate how AWS Lambda is always-on for our functions, with only a brief "cold-start" waiting period the first time a function is called after being dormant.
• In addition to only generating costs when it's actually being used, AWS Lambda really puts the "serverless" in serverless architecture, offering turnkey scaleability and high availability for our code with zero effort on our part.

Read full review

• Keeps things more standardized, ring fenced and thus easier for the end user to use
• Open source, allowing for a wide group for education, auto and support
• Developing at pace to keep up with the ever changing needs of the industry from on / off premise, public and private

Read full review

• The UI and Developer experience is not so great. IF you use an abstraction like Serverless Application Model (SAM), things get pretty easy, but it's still AWS UI/DX you're working with after that (which is to say, not their strength).
• Documentation is always a mixed bag. Sometimes it's just easier to google your specific problem and see how others have solved it. This can be much faster than trying to find an example that may or may not be there in the documentation (which oftentimes has multiple versions and revisions).

Read full review

• Sometimes the API Connect GUIs don't cleanly disengage after attaching models or updating schema and it is hard to know what has been written successfully and which (if any) models or tables were missed. I shouldn't have to manually check through a list of 377 models to find the ones in and out of a list on either models, folder or database tables. Printing a summary even in logs which did a "diff" sort of thing between 'task-set' and 'task-completed' (referring to attaching models or updating schema as tasks here as 'tasks').
• Provide access to Postgres Database in Sydney datacentre for Australia.
• Clearer documentation around setting up a secure (referring to SSL and certificate setup here) server on eg, chubby1.au-sydney.mybluemix.net.
• Allow a ramp in pricing onto the Blockchains. We will not be able to afford it until quite a few years into production, even if we launch successfully.

Read full review

• I was able to perform a lot of processing on data delivered from my website and little or no cost. This was a big plus to me.
• Programming AWS Lambda is quite easy once you understand the time limits to the functions.
• AWS Lambda has really good integration with the AWS S3 storage system. This a very good method of delivering data to be processed and a good place to pick it up after processing.

Read full review

• Bluemix has allowed me to effectively serve the App industry more recently, especially with the new visual design implemented recently.
• BlueMix offers a lot more customization of the Platform, rather than Infrastructure, giving me a big edge over other companies offering only AWS or Azure cloud services, and brings a lot more apparent value to my business.
• The additional features, especially the Watson service subset offers a HUGE range of new and innovative technologies, especially in the realm of AI, that encourages my clients to test out new potential features, which leads to more sales as they increase there platform size and capability.

Read full review