By me
I get the logic of having functions as a whole, like offering at a service.
My issue is the logic in how it’s been deployed. As I understand from the documentation, you test your function inside functions. Then when you’re ready to deploy it to production use, you deploy the function as a app component. So basically the functions service is for development use only.
Why not call it app component testing or something. Am I missing something? The logic seems half baked. Like the idea makes sense, small functions to have and API to send requests to. But how it was built out as a service inside DO doesn’t make sense.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there,
Serverless functions are not really a new concept invented by DigitalOcean. Serverless functions as a single-purpose, programmatic feature of serverless computing concept has been there for a while, offered by all main cloud providers. I believe that the feature is a good addition to the DigitalOcean set of products, making their offering way more complete.
Here are a few good resources to help you better understand what the main benefits of serverless functions are:
Hope that this helps!
Best,
Bobby
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.