5 ms·

Anything on the roadmap for supporting server-side (api, db, etc.) in the same way?

by biot 9y ago

marktangotango 9y ago
There are a few things you can do from static sites; authorization services, database as a service, backend as a service, etc. I find people find theses things appealing in the abstract yet rarely build anything with them. I built a dbaas that failed myself. For example, what dynamic functionality would you like to add to your dynamic site?
- biot 9y ago
  I'm thinking of explicitly non-static sites, enabling SaaS offerings. I'd like to see the ease of use and functionality for static sites extended across the full stack.
  - marktangotango 9y ago
    I'm working on something along these, lines. If you or anyone else is interested in early access, please contact me (email in profile).
_fool 9y ago
Disclaimer: I work for Netlify If you check out this blog post about one of our biggest customers, you can see that there are some non-static services involved (look for the list of 4 services all called Go<something>): https://www.netlify.com/blog/2017/03/16/smashing-magazine-just-got-10x-faster/ https://www.netlify.com/blog/2017/03/16/smashing-magazine-ju... So - while I wouldn't say we're planning to become a DB host or anything - we are both open to providing some glue needed to bring some missing pieces together for static sites without vendor lock in (all of those are open source and you can run your own instances - they are also all being polished up right now so keep an eye on the one(s) that interest you)...and we are trying to enable other services we don't want to reinvent - things like auth0 and firebase - for interoperability with our service. oh yeah, and we also open sourced a CMS that uses Git as a backing store so your content editors won't have to learn markdown or git... https://github.com/netlify/netlify-cms https://github.com/netlify/netlify-cms So - we're not done yet :)

Anything on the roadmap for supporting server-side (api, db, etc.) in the same way?

by biot 9y ago

Anything on the roadmap for supporting server-side (api, db, etc.) in the same way?

There are a few things you can do from static sites; authorization services, database as a service, backend as a service, etc. I find people find theses things appealing in the abstract yet rarely build anything with them. I built a dbaas that failed myself. For example, what dynamic functionality would you like to add to your dynamic site?

biot 9y ago
I'm thinking of explicitly non-static sites, enabling SaaS offerings. I'd like to see the ease of use and functionality for static sites extended across the full stack.
- marktangotango 9y ago
  I'm working on something along these, lines. If you or anyone else is interested in early access, please contact me (email in profile).

_fool 9y ago

Disclaimer: I work for Netlify If you check out this blog post about one of our biggest customers, you can see that there are some non-static services involved (look for the list of 4 services all called Go<something>): https://www.netlify.com/blog/2017/03/16/smashing-magazine-just-got-10x-faster/ https://www.netlify.com/blog/2017/03/16/smashing-magazine-ju... So - while I wouldn't say we're planning to become a DB host or anything - we are both open to providing some glue needed to bring some missing pieces together for static sites without vendor lock in (all of those are open source and you can run your own instances - they are also all being polished up right now so keep an eye on the one(s) that interest you)...and we are trying to enable other services we don't want to reinvent - things like auth0 and firebase - for interoperability with our service. oh yeah, and we also open sourced a CMS that uses Git as a backing store so your content editors won't have to learn markdown or git... https://github.com/netlify/netlify-cms https://github.com/netlify/netlify-cms So - we're not done yet :)