RichardExley
RichardExley
Enhance Availability of Microservices Implementations to behave appropriately during the following outages: - Unplanned: Database, Database Instance, Microservice Instance, Load Balancer, Ingress Controller - Planned: Database, Database Instance, Microservice Startup...
Using only database technology, construct all the Grabdish microservices. Ideally, they would be written entirely using MLE JavaScript running in the database and exploit the existing ORDS and APEX technologies...
Continue the refactoring of the code to support: - Development and Setup on Cloud Shell, Linux, MacOS and Windows - Reuse by multiple workshops - ATP and non-ATP database -...
ATP on shared infra does not support FAN. We need to have a mechanism to turn off FAN in our microservices when connecting to ATP-S. In the Python and NodeJS...
The build is failing. This is new this week. I tested in my tenancy and live labs with the same result. ` gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -g -pipe...
Known anomalies: - Free trial uses VM.Standard.E2.1, LiveLabs uses VM.Standard2.1. Ideally they would be the same. What to do? - VM.Standard.E2.1 shapes became "End of orderability" in Feb 2021. We...
It took me a few minutes to actually find the generated yaml as the deploy.sh refers the user to # See docs/Deploy.md for details which at the end of the...
Microservices should not crash if the database is temporarily unavailable. Functions that do not require the database should remain available. Database connections should gracefully switchover to a surviving instance on...
ATP-S does not support FAN and so services should not connect with events. If they do, connection time is very long.