3 ms·

There are two offers: 1) normal pharo cloud 2) ephemeric The cloud offer with the price you cited is similar to running pharo on you own virtual linux machine

There are two offers: 1) normal pharo cloud 2) ephemeric The cloud offer with the price you cited is similar to running pharo on you own virtual linux machine. The ephemeric cloud is different: it uses pharo images themselves as containers and provides a simple Rest API to start them up. Cost is $10 for up to 20 running images, the free account gives you already one to play. The difference is that the ephemeric image is never saved, gets automatically killed after 30 minutes (and restarted when needed).

IanCal 11y ago
Just to clarify the "gets automatically killed after 30 minutes (and restarted when needed)" that's 30 minutes of inactivity, and gets restarted when a new request comes in. > First, an Ephemeric application is "paused" after 30 minutes of inactivity. It means that the Pharo Image is stopped and all the associated resources are removed from the memory. Ephemeric Cloud is designed specially for web solutions hence by "inactivity" it is meant no HTTP requests sent to the Ephemeric. The system automatically starts the Epehemric application upon the next request so for the user it looks like it was never off. https://www.pharocloud.com/kb/tutorial/ephemerics-introduction https://www.pharocloud.com/kb/tutorial/ephemerics-introducti...
390487823r4 11y ago
How fast is the restart after it gets killed? I am thinking of brochure sites using SandstoneDB. What is the best way to save data to be loaded into SandstoneDB - class-side methods perhaps?
- mikefilonov 11y ago
  The restart is like 5 seconds or so. Of course, it depends on Image. Please keep in mind that Ephemeric instances are not able to save data to a local disk, so there will be restrictions on using SandstoneDb. To store data you may run Mongo DB and configure a secure channel from the ephemeric or just use Pharo appliance at Pharocloud - with disk, no restarts and without other ephemeric restrictions so you will be able to use SandstoneDb on a full scale.

IanCal 11y ago

Just to clarify the "gets automatically killed after 30 minutes (and restarted when needed)" that's 30 minutes of inactivity, and gets restarted when a new request comes in. > First, an Ephemeric application is "paused" after 30 minutes of inactivity. It means that the Pharo Image is stopped and all the associated resources are removed from the memory. Ephemeric Cloud is designed specially for web solutions hence by "inactivity" it is meant no HTTP requests sent to the Ephemeric. The system automatically starts the Epehemric application upon the next request so for the user it looks like it was never off. https://www.pharocloud.com/kb/tutorial/ephemerics-introduction https://www.pharocloud.com/kb/tutorial/ephemerics-introducti...

390487823r4 11y ago

How fast is the restart after it gets killed? I am thinking of brochure sites using SandstoneDB. What is the best way to save data to be loaded into SandstoneDB - class-side methods perhaps?

mikefilonov 11y ago
The restart is like 5 seconds or so. Of course, it depends on Image. Please keep in mind that Ephemeric instances are not able to save data to a local disk, so there will be restrictions on using SandstoneDb. To store data you may run Mongo DB and configure a secure channel from the ephemeric or just use Pharo appliance at Pharocloud - with disk, no restarts and without other ephemeric restrictions so you will be able to use SandstoneDb on a full scale.