AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
Genesys Cloud CX
Score 8.5 out of 10
N/A
Genesys Cloud CX (formerly PureCloud, Genesys Cloud) is a contact center application optimized for automatic call distribution, interactive voice response, email, social media, chat, and text/SMS. It is also a VoIP interconnect service provider.
$75
per month (billed annually) per user
Google App Engine
Score 8.2 out of 10
N/A
Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for …
Amazon Connect wasn't listed in the above list. We were previously using PureConnect. We assumed the transition would be easier because we had great support from our Genesys Partner (Wrendata). We liked the app foundry add-ins.
For our organization, we selected Google App Engine which provides a reliable and efficient way to create and deploy apps moreover it supports a lot of languages and provides automatic debugging of code which enables us to deploy code to production as soon as development is …
If you have a small team which is also responsible for development of the product then surely go for it. And if you have a larger team with dedicated person to take care of deployments. Go for cheaper options such as compute engine or AWS (be sure to do your research on pricing …
You can create and scale Kubernetes clusters quickly, but you have to keep an eye on that cluster. In-App Engine, you don't have to worry about infrastructure, but in some scenarios, Kubernetes fits better.
Azure App Service is in par with Google App Engine although you may want to use Azure App Service if you are integrating with other Microsoft IT components, for example SQL Server. Google App Engine is great when in long run, you will be using Google cloud components, for …
The two giants are Google and Amazon. Both are very similar however Google App Engine allows you to deploy your web applications through platforms like Python where as if you're using AWS, you have full control on the operating system services. Google is good because you pay as …
I think that Microsoft and Amazon are simply investing more in their offerings, and there are a bunch of cool PaaS solutions out there as well. Google App Engine is solid, and is probably the right choice for some projects. But ultimately one should evaluate each platform …
Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
The Data table provided in Genesys cloud which is very useful, dynamic and easy of operations team on their day to day changes in menu prompts, priority, etc. With the routing methods we have, we can use preferred routing initially for our contact centre and if no suitable agents are available, we can expand the routing ring and can go wide and look for more suitable agents. These are some of the scenarios in which Genesys cloudCX came in handy.
App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
There is a limit of 5 Audiohook monitor integrations for Genesys, which could have been more.
Genesys customer support could have been more proactive and helpful, similar to other major companies like Salesforce and AWS. However, whenever I raised a concern, in most cases, they would directly tell me it was a custom requirement, so I should post in the dev community or contact their Professional Services (PS) team.
In the Genesys Dev community, if you post any of your problems, it's unlikely that they will be noticed, and you will likely not receive a resolution to this issue. Moreover, if no one replies to you within 30 days, that post of yours will also be closed.
There is a slight learning curve to getting used to code on Google App Engine.
Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
The upcoming upgrades working with Genesys Cloud and Salesforce are very exciting. Even though we don't use Genesys Cloud to the fullest extent it can be used (we just migrated a year ago), when these upgrades roll out, I am very excited to see what it can do to for our agents. I think they are going to be very impressed
App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
Everything is very good. It is very useful, friendly to users and it makes our work easier than what we expected. I think that I don't need any help from someone on how to use Genesys coz basically they will directly feed it to you without any hassle on using it.
I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
The platform is highly reliable, with minimal downtime or outages, and is generally available when needed. Over the course of using it, unplanned outages or application errors have been rare, and any issues that did arise were quickly resolved. Genesys provides robust support and maintenance, ensuring the system remains operational during critical business hours. However, like any cloud-based platform, there have been occasional disruptions, though these were infrequent and quickly addressed. Overall, its availability has been excellent, supporting smooth daily operations.
Overall, the platform performs well, with pages loading quickly and reports typically completing in a reasonable time, even with complex data. The interface is responsive, and most day-to-day tasks are executed efficiently. However, in some instances, especially during peak usage times or when running very detailed, large-scale reports, there can be slight delays. While these are rare, they occasionally affect workflow. Additionally, the platform generally integrates smoothly with other systems, though some integrations can slow down slightly, particularly when pulling large datasets or interacting with older, legacy systems. Nonetheless, the performance is strong and reliable for most use cases.
Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
Support does indeed resolve the issue but they seem to be really slow and I have to stay on them to get my ticket handled. Everyone I have interacted with is very professional and pleasant. Other than being slow its been a good experience
Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
Genesys team that provide trainings are friendly and professional. They helped us to understand well the product and the functionalities. The training was detailed with use cases. At the end, we got a task to develop that ended with success and we got some Genesys rewards. It was amazing experience
In general, it gives a description and can help to understand what to do and how. but: Sometimes, it does not keep up with changes in the system (for example, in the GUI changes, additional features and so on). Sometimes, much easier and helpful to read the documentation (https://help.mypurecloud.com/) that gives the "better" explanations and takes less time.
The first engineer that we had work with our team was not able to grasp our needs. However, Genesys Cloud CX quickly replaced that person with an overqualified engineer who joined our implementation team because he wanted to support our work.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
Genesys Cloud CX offers the most mature all‑in‑one, cloud‑native microservices platform with strong AI, orchestration, and omni‑channel depth. Webex Contact Center is improving rapidly but remains relatively new, with strengths in Cisco ecosystem integration and enterprise UC alignment. Five9 provides a reliable, scalable CCaaS with strong global redundancy and mature telephony, excelling in high‑volume voice‑centric operations. Overall, Genesys leads in advanced CX/AI, Webex in UC integration, and Five9 in voice resilience.
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
Genesys provides Licensing in 3 tier subscription types of licenses on top based on any business requirements then any sort of feature/functionality inclusion (or removal) is discussed openly. There are 2 types of billing models available which are "Named" and "Concurrent" based on the type of roles users will perform in Genesys Cloud CX environment (eg. Agent, Supervisor, Administrator, and Business Users) Also, the billing period/frequency starts on the actual day the platform is delivered.
I give Genesys a rating of 10 for scalability because of its ability to adapt seamlessly to growing business needs, whether expanding across multiple departments, locations, or regions. Its cloud-based infrastructure allows for easy scaling without the need for costly hardware upgrades or lengthy implementation times. As our organisation grew, we were able to add new agents, channels, and features without disrupting operations, which significantly enhanced our flexibility. The platform's design supports both small-scale and enterprise-level operations, making it ideal for evolving businesses. Additionally, its capacity to handle increased interaction volumes without compromising performance ensures that customer service quality remains high, even during peak times. This flexibility and ease of scaling, combined with real-time analytics and automation capabilities, make it highly effective for growing organisations.
Professional services are definitely much more experienced than the support teams, and the price for their services is very fair. I wish that the support team could help answer simple questions about work that the PSS team does, however, so that we do not have to use our SOW for simple Q&A emails.
Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.
Strategic Agility- Genesys Cloud CX has delivered both immediate cost benefits and long-term value through improved customer relationships, operational resilience, and administrative satisfaction.
Enhanced Customer Experience- With advanced analytics and personalized interactions, we’ve seen an improvement in routing to address customer needs.
Cost Savings and Operational Efficiency- The platform’s cloud-based architecture can eliminate on-premise infrastructure and maintenance in some cases.
Effective integration to other java based frameworks.
Time to market is very quick. Build, test, deploy and use.
The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.
