We are looking for a Senior Backend Golang Engineer, who will help us improve the most advanced content management system worldwide. As a Backend Engineer at GraphCMS, you will take care of extending and solidifying our backend architecture.
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.
the former GraphCMS was built on top of Graphcool, with the new system, we also move to Graphcool's new product, Prisma, which is a setting we enjoy a lot. Prisma runs at the core for CRUD and then we add an additional API layer to it to add the features we think make sense in a CMS context.
The value add depends on perspective. If you are looking for a tool to build a content database, then GraphCMS brings definitely a lot to the table. While you get the content management interface and tools, we add just enough opinion to the APIs that makes sense in a context of building a content database.
Graphcool is also not actively maintained anymore as the team is now focusing on Prisma.
The Demo-API on the landing page is from the former stack. We will soon add a new example to showcase all the new API utils.
GraphQL is fun on the frontend. On the backend, there is a gazillion things that need to be considered. You can build a powerful GraphQL backend via the GraphCMS UI.
So we leave you with the fun part.
This has proven very valuable to our users that don't want to implement the backend part of things, while getting a content management interface for editors.
Nothing is wrong with plain old HTML. Going headless gives you frontend freedom. It means integrating your content on any platform you like: web, mobile, smartwatch, fridges and toasters (if they are smart enough). It's interesting that we mostly see people using a headless CMS just for web.
Why?
Because they can pick the frontend stack they like! React, react-static, Gatsby, vue, nextJS etc.
You can pick the stack you like most. It is much easier to find a react developer than someone who knows how to write good drupal templates.
Why GraphQL? Because it's awesome! I can highly encourage you to just try out a GraphQL API and see yourself. It is designed for fetching related data efficiently and it will give you a huge boost in development productivity, which means lower development costs and faster time to market.
Our new architecture allows much more flexibility on the deployments, so just speak to us about your favorite setting. However, it is quite complex and we rather focus on delivering a high quality cloud infrastructure that works for everyone. I can understand your perspective but our mantra is to remain a SaaS company, which means to be able to focus on ONE code base. This allows us on delivering a higher quality product in the long run so all users can benefit from it.
