Their functions are also limited to triggers relating only to Netlify events: https://docs.netlify.com/functions/trigger-on-events/#availa...
to be clear the functions are also exposed to the public internet as http endpoints so you can ping them from anywhere else, including, for example, your frontend app, or Zapier [1], or GitHub Actions or cron service of your choice
(i work at netlify)
1: https://www.netlify.com/blog/2018/11/07/automate-your-netlif...
They did a very good job at marketing "HTML5 hosting"
If you forget that then Cloudfront will retrieve the objects from S3 every time there is any activity on your site and your bill will go up really fast.
For how long? I remember I got something similar for AWS for a year. Hosted my Wordpress, year passed, then prices jumped up. I migrated to Netlify, rebuilding my site as a static one, hosted for free now.
That sounds awful. How do you share any of your common logic? Do you have to write versions of your important routines once in each language, each with its own set of quirks and bugs?
It's bad enough in microservice land, where every time you want any shared code you have to extract it to a e.g. "utils" library and massage the versioning to get it in to the right apps.
End result: most people don't and you end up with many different little versions of your routines that do important things.
In our case the limitation is less about the monolith architecture and more about our team’s unwillingness to learn a new language.
Sounds nasty. The classic python answer is to try rewriting the innermost loops in cython/c/cppyy etc or try using numba/pypy.
> best language for the job
The problem with this "best ... for the job" phrasing is that there's an objectively, indisputably right answer, where I've experienced atrocious choices being inflicted upon a team under that guise, resulting in a component that nobody wants to maintain because it's foreign to everyone.
Yep, we’re doing this. The problem is that we’re still calling back and forth between C and Python very frequently and rewriting that next layer in C or similar is prohibitively unmaintainable.
> The problem with this "best ... for the job" phrasing is that there's an objectively, indisputably right answer, where I've experienced atrocious choices being inflicted upon a team under that guise, resulting in a component that nobody wants to maintain because it's foreign to everyone.
Fine, then let’s at least not use the wrong tools for the job, in this case, Python and language’s that impose similar tradeoffs.
Yes - the trick really is to move your accelerated code away from python's object model, because then you can drop a lot of overhead and also release the GIL. Tricky, though. Out of interest, did you see any improvement from pypy or numba?
> prohibitively unmaintainable
I don't think well written cython should be any more unmaintainable than Go IMHO.
> I don't think well written cython should be any more unmaintainable than Go IMHO.
I've written a lot of Go, it's always struck me as about as maintainable as Python (I would put it at a bit more maintainable than Python given its mature static typing story--mypy still has lots of problems). I haven't given Cython a fair shake, but it doesn't seem very well-invested in; this is generally what has kept me away from it.
Of course. It's just managed by someone else and you often are paying per usage. And you'll find yourself needing to wrangle numerous serverless platforms to actually build out relevant business logic if you want to do something meaningful, one third-party microservice at a time.
> Also, because it's just a static site, there's no backend or database, so you get better security.
It's not as trendy to think of it this way, but "static sites" are just caches with manual invalidation.
Thinking of it as a cache has some merit, but it is more exciting to think of it as a event driven system as a whole, where instead of triggering a render on demand (user wants to look at something) you trigger it when a change happens.
This pattern reduces the need for ad hoc caching and eliminates some accidental complexity as well because it reduces the coupling of management and representation.
I deploy my React apps and landing pages there and don't need to worry about the underlying compute, or load balancing, or anything else. Thankfully I didn't do any frontend work before Netlify was available!
I don't really get all the hype around the Jamstack (https://jamstack.org/), though.
Netlify's hypothesis seems to be that if you deploy websites on CDNs, instead of on web servers, then you'll get better performance.
Also, because it's just a static site, there's no backend or database, so you get better security.
I accept this hypothesis, but it seems like you still need a backend. Netlify is promoting functions as a service [1] so you can avoid having web servers for the backend too, but I'm a little skeptical you get the flexibility to build applications with dependencies or non-trivial business logic or design with this approach.
If anyone's tried a FaaS and this is incorrect, please describe your experience!
[1] https://www.netlify.com/products/functions/