How to easily write and maintain functions in a cloud-agnostic way
Although the term serverless computing will not win the award for the clearest terminology, it is one of the recent buzzwords in IT. It is more than a buzzword, though, and it is a very relevant concept for developers writing software that is intended for use in production in cloud environments.
From On-Premises Monoliths to Serverless Functions
One of the main reasons why companies are moving their operations from on-premises servers in their own data centers to centrally managed cloud systems is the cost reduction. Buying and maintaining servers can be very expensive and really makes sense only from a cost perspective if the servers are used at their maximum capacity for most of the time.
In most real-world situations, though, companies experience peak loads during which the available servers cannot handle all requests fast enough. During quiet moments, there are too many servers doing nothing.
The initial cloud offerings allowed you to add and remove servers when required. That implies a cost reduction for many companies, but servers are still kept running (and they have to be paid for). In many cases, the servers are capable of executing more requests, but there are fewer incoming requests, so the servers are mainly just waiting for work. Due to the granularity (the server is the unit norm), this is not really "pay per usage."
Using container technologies such as Docker, it became easier for developers to write software in their own environment and deploy the same software in the same environment on cloud servers. Using container management software, it is even possible to scale servers when needed.
But still, the unit at which "pay per usage" applies is still the server. It would be more cost efficient for cloud users if the billing unit were based on real server usage. Changing the billing unit to the amount of time a function is running is a big step closer to "pay per usage." Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.