Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: GraphCMS – A GraphQL-based Headless CMS

graphcms.com

Post reply on HN
Print view View original

51–60 of 70 posts

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#51

Post by ltrcola »

everdev wrote: post #21
arpinum wrote: post #9

Earlier quoted context omitted.

Squidex is MIT license and has reasonable pricing for their cloud offering, also has graphQL support and more feature rich.

I'm not a fan of pricing with operation limits. 100k API calls per month? What happens in a DoS situation? If it's self-hosted I can blacklist and keep the app running for other users. For a surge in traffic, I can spin up other containers and scale. With managed hosting, my bill can go through the roof, or the the entire app gets shut down.

Ideally, a spike in traffic to your site shouldn't result in taking down your CMS. That's why static site generators are so popular.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#53

Post by everdev »

ltrcola wrote: post #51
everdev wrote: post #21

Earlier quoted context omitted.

I'm not a fan of pricing with operation limits. 100k API calls per month? What happens in a DoS situation? If it's self-hosted I can blacklist and keep the app running for other users. For a surge in traffic, I can spin up other containers and scale. With managed hosting, my bill can go through the roof, or the the entire app gets shut down.

Ideally, a spike in traffic to your site shouldn't result in taking down your CMS. That's why static site generators are so popular.

Exactly, but many of these 3rd party services charge per API request, which can either shut down your service or spike your bill during heavy traffic.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#54

Post by mlukaszczyk »

intrasight wrote: post #47

I reviewed the site. I still have no idea what GraphCMS does.

TLDR; It allows you to bring content to any platform.

It allows you to build content databases in an easy and visual manner. Once you have your content in GraphCMS, you are able to fetch it in an elegant way by using GraphQL. The target platforms that consume the content can be anything: web, mobile, alexa skills or just business partners you want to share digital content with so that they can put it on the target platform of their choice.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#55

Post by ltrcola »

everdev wrote: post #53
ltrcola wrote: post #51

Earlier quoted context omitted.

Ideally, a spike in traffic to your site shouldn't result in taking down your CMS. That's why static site generators are so popular.

Exactly, but many of these 3rd party services charge per API request, which can either shut down your service or spike your bill during heavy traffic.

Not sure if I communicated what I meant. I think if I was going to set up something using a headless CMS, I would integrate it with a project like React Static. When a user publishes something in the CMS, it would trigger a build of the generator that would result in putting some files out in S3 or something equivalent.

That way if you see a traffic spike or a DDoS attack, it's directed only towards static files on S3 and you can let Amazon take care of it. I don't want to be too critical of how people have things set up because I'm sure they have their reasons, but that said I don't think a page request on your site should map directly to an API request to the CMS.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#57

Post by pippy »

jordanlev wrote: post #40
neeksHN wrote: post #2

It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab

There are lots out there, but the terminology is not consistent so it's hard to identify them. Perhaps one of these would serve your needs: https://strapi.io https://getcockpit.com

And to add to your list: SilverStripe framework 4.0. Their PaaS solution is pretty pricey, but it's opensource so you can run it yourself.

Their software ecosystem is mature as well, as they've been around for a while.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#58

Post by wishinghand »

ksec wrote: post #31

Excuse my ignorance, and I don't mean to troll. Why would I want a "Headless" CMS? Why would I want a CMS based on GraphQL? What is wrong, with plain old HTML?

A Headless CMS means you define all of the frontend interpretation of the content. Basically a GUI for your database.

If you have lots of queries happening behind the scenes whenever someone makes a request that seems basic- like how Facebook gets a list of comments on a post, plus the friends who made them, and a list of different reactions to each comment, and other stuff that rapidly creates a complex graph- then GraphQL simplifies. The REST way involves all of those extra calls, GraphQL gets everything in one request.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#59

Post by atom_arranger »

les wrote: post #10

The scary thing to me is if a service like this stops, I have an angry client and a lot of work. Headless CMS's are a delight to work with though.

I've run into this recently. We're exploring using headless Wordpress for some static sites. Seems to work pretty well.
Post reply on HN