{"id":378800,"date":"2021-06-17T02:04:44","date_gmt":"2021-06-17T09:04:44","guid":{"rendered":"https:\/\/www.genesys.com\/?page_id=378800"},"modified":"2024-02-01T16:55:07","modified_gmt":"2024-02-02T00:55:07","slug":"faq","status":"publish","type":"page","link":"https:\/\/www.genesys.com\/en-sg\/faq","title":{"rendered":"FAQ"},"content":{"rendered":"

[vc_section g_section_text=”white” css=”.vc_custom_1594761997072{background-color: #4e5054 !important;}”][vc_row][vc_column][vc_column_text]<\/p>\n

Genesys Cloud platform FAQ<\/h1>\n

[\/vc_column_text][\/vc_column][\/vc_row][\/vc_section][vc_section][vc_row][vc_column width=”2\/3″ offset=”vc_col-sm-offset-2″]

<\/i>✖<\/span><\/a><\/div><\/div><\/div>

Genesys Cloud\u2122 is a platform?<\/h3><\/i><\/div>

Genesys Cloud has been designed as a platform since its start in 2012. We knew we\u2019d add new developers as we grew, so we built clean APIs with plenty of documentation.<\/p>\n

We knew we couldn\u2019t predict all the future needs, so we built extensible systems and API calls to efficiently add on new data and functionality. We\u2019ve been active each week making decisions about services and testing, because great architecture doesn\u2019t happen all by itself. Finally, we knew we couldn\u2019t \u2014 and shouldn\u2019t \u2014 try to cover everything for everyone. We built a robust core with tools to extend it into whatever you might need. In other words: Genesys Cloud has always been a platform<\/strong><\/a>. <\/strong><\/p>\n<\/div><\/div><\/div>

How is Genesys Cloud different from other cloud platforms?<\/h3><\/i><\/div>

Genesys Cloud is the original built-for-the-cloud customer experience platform. We don\u2019t grow by bolting on acquired technology. Instead, our developers rewrite and convert new functionality into the platform and add their services to the APIs. We\u2019re continually testing and releasing through a DevOps automation framework for CI\/CD. And we focus on building a truly robust service-oriented architecture<\/strong><\/a>. <\/strong><\/p>\n<\/div><\/div><\/div>

How do I get started developing on the Genesys Cloud platform?<\/h3><\/i><\/div>

If you have an authenticated organisation and a development environment, we can help with our Developer Centre Quickstart<\/strong><\/a>. You can also try Genesys Cloud for free<\/strong><\/a> with a \u201cno risk, no commitment” 30-day experience to see how it works.<\/p>\n<\/div><\/div><\/div>

How fast is the platform advancing?<\/h3><\/i><\/div>

We release 1,000 or so small updates each week and more than 300 feature updates a year. Current logs show that 100% of our code is replaced every 14 days (often faster). Deployments occur across all regions and locales. There\u2019s only one version of the Genesys Cloud platform in production at any given time. This allows us to test \u2014 massively and thoroughly \u2014 any code change as it progresses through multiple staged environments before it\u2019s deployed.<\/p>\n

Major feature updates, also known as \u201cepics,\u201d are broken into hundreds of smaller changes with feature flags controlling access. By the time a new feature is made available, it has been in the system under continuous testing for several weeks. See what\u2019s new in Genesys Cloud<\/strong><\/a>.<\/p>\n<\/div><\/div><\/div>

How do you keep Genesys Cloud stable, considering all the changes and growth?<\/h3><\/i><\/div>

We\u2019re obsessed with resilience. Of course, we work hard to build and test for stability, but in the real world, things always fail. You can continually \u201charden\u201d a system and it will still fail. True resiliency is a different approach.<\/p>\n

When we detect a problem, we check dependencies and restart the process to complete your response before you notice. A failure is temporary and caught before it has any impact to you or your customers. We log and analyse issues, and we make improvements all the time to eliminate those problems in the future. For example, we add past issues to our test automation to make sure they\u2019re caught before they\u2019re promoted. A cloud with an event-driven architecture and microservices gives us the tools needed to build these self-healing systems.<\/p>\n

Resiliency is an integral part of our development culture. We challenge our developers with a work environment that includes ongoing, intentional and randomly induced failures. Developers can see whether their systems recover and why with automatic reporting. Using this perspective, we adjust how we code \u2014 and we do this all the time. You can see proof of how we work on the Genesys Cloud status page<\/strong><\/a>. <\/strong><\/p>\n<\/div><\/div><\/div>

If a customer (IT\/developer) builds custom code for Genesys Cloud, how can we keep up with the continuous deployments?<\/h3><\/i><\/div>

Some people more directly ask, \u201cAre your updates going to break our code?\u201d No, that\u2019s not our intent. While we try not to fall in love with our code, we know that everything changes. We embrace change, but in a way that doesn\u2019t break old code (at least, not without extensive time and full transparency). We spend a lot of time and effort focused on the following efforts, because we\u2019re also using the same APIs.<\/p>\n