Live data from Hacker News

Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog

paulie.dev

1–10 of 22 posts

Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog

#4

Not sure if using 3rd party services for a CMS is a good idea. What happens if this API or Netlify goes down? Doesn't seem reliable.

You are always relying on a 3rd party somewhere down the stack that's not a reason to dismiss a solution alone.

Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog

#7

Not sure if using 3rd party services for a CMS is a good idea. What happens if this API or Netlify goes down? Doesn't seem reliable.

If the Twitter API is down, then you'll have blank spots on your page where there are supposed to be tweets.

If Netlify goes down, you won't be able to publish, but your statically rendered site should still load just fine unless you are using it to make dynamic queries on the fly (which is, I think not generally done for Gatsby, but very possible to do)

Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog

#8

Not sure if using 3rd party services for a CMS is a good idea. What happens if this API or Netlify goes down? Doesn't seem reliable.

You are always relying on a 3rd party somewhere down the stack that's not a reason to dismiss a solution alone.

Given Twitter's track record on APIs, there is every reason to dismiss this solution.

Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog

#10

Earlier quoted context omitted.

You are always relying on a 3rd party somewhere down the stack that's not a reason to dismiss a solution alone.

Given Twitter's track record on APIs, there is every reason to dismiss this solution.

To be fair, this is something they've acknowledged and committed to working on for future API iterations.
Post reply on HN