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!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
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!