Some time ago we deprecated the programming problem code parameter (
problemCode) as its primary unique identifier. We decided that the programming problem ID (
problemId) should become the recommended identifier of the programming problem. At the same time, the value of this ID was not properly presented in the interface of the Sphere Engine Problems Editor. This is why we have introduced a dedicated column for it on the programming problems list in the Editor. Additionally, both the code and its ID are now visible on the specific programming problem page in the Editor.
We continuously monitor the efficiency and reliability of Sphere Engine services, yet, there is always room for improvement. Recently we have introduced many fixes that increased both the precision and the response time when it comes to detecting issues inside our cloud infrastructure.
Some questions need to be addressed! If a question is asked frequently, then we answer it in (well, you’ve guessed it :)) our FAQ section. We have covered three new questions - two of them on the topic of CORS that accompanies the integration of the Sphere Engine APIs. The answer to the third question explains that in case of a temporary lack of resources needed to run a program, there is a queue in which all programs safely wait for available resources (without any expiration time).
We have updated the information about supported programming languages and added some missing details in the Features section of selected languages.
At Sphere Engine we combine years of experience in recruiting developers and assessing coding skills with the latest technologies. Our APIs and software components enable creating programming challenges, online compilers, IDEs, and teaching coding to millions of end-users across the globe. We work with companies like Infosys, Amazon, Edhesive, support thousands of educational institutions around the world, and run our own community-focused platforms - Spoj and ideone.