Headless CMS

Definitions & benefits

Tools & Concepts

Open source

Features

Authentication

Custom plugins & Marketplace

Webhooks

Multilingual CMS

APIs

Dynamic Zones

User roles & permissions

Content Modeling

Security & Privacy

Use Cases

Ecommerce

Blog

Forum

About Strapi

Life at Strapi

Releases & Roadmap

Events

Community

News

The Tutorials section covers an introduction to Strapi, some advanced technical content, product updates and releases. From basic workaround to in-depth development guides. 

Tutorials

How tos

Get all the latest updates, news and events.

Subscribe to the newsletter 📣

Saying that Internet-based technologies are everywhere would be quite the understatement. They have indeed permeated almost all aspects of our lives, arguably changing things for the better, and continue to lead and support innovation. 

At this point, those who decide to run a web project find themselves virtually overwhelmed by the plethora of solutions at their disposal to make housing and publishing their work a mere formality. **Cloud computing services** are one such option and host applications online, giving them a ‘home’ to operate from. This could be a simple answer to the question ‘What is Heroku’ or ‘What is AWS’. In practical terms, however, cloud computing services do have their own sets of characteristics which make them more appropriate for certain tasks.

## What is Heroku

![What is Heroku](/uploads/What_is_Heroku_ed54b5d4e5.png)

Heroku is a **cloud-based PaaS (Platform As A Service)**, customers can use to build, scale and deploy their own web applications. As a cloud service provider and software development platform, it offers a fast and effective solution that comes complete with over 175 add-ons. These cover a variety of needs ranging from security alerts to monitoring tools, caching, mailing, networking, etc. It is considered a user-friendly container-based platform. What is Heroku’s greater strength? Probably the fact that it is not as open-ended as certain options, though there is also, as we will see, a downside to this fact. This is why [API developing solutions](https://strapi.io/) – such as **Strapi** – choose to provide programmers with other alternatives. Heroku is perfect if you wish to migrate and start your apps quickly and easily, but you will not be given access to the PaaS’s underlying infrastructure. Though, admittedly, those who seek a ready-made environment to deploy their apps typically have no use for such access.

## What Is AWS?

![What is AWS](/uploads/What_is_AWS_2499871957.png)

Amazon Web Service – also known as AWS – offers a wide array of **cloud computing services**. It provides a powerful solution for developers and combines databases, analytics, storage, deployment, management, delivery, and more. It is a full-fledged Infrastructure As A Service (IaaS) platform that supplies an entire infrastructure consisting of virtual machines, virtual networks, and many more features users can access for their own needs. Several PaaS components are available including Amazon Container Service (AWS ECS), Fargate, Beanstalk, etc. These options are so advanced that even tech giants like Ubisoft or Airbnb turn to Amazon Web Services. [What is Heroku](https://strapi.io/documentation/3.0.0-beta.x/deployment/heroku.html) truly comparable to in this context? There are in fact some key differences between Amazon’s IaaS platform and Heroku’s PaaS solution.

## What Are the Main Differences Between Heroku and AWS?

Choosing between PaaS (Heroku) and IaaS (AWS) is rarely a question of personal preference, as these two solutions do not really address the same needs. With PaaS, you can benefit from a suite of **ready-made tools** that are very convenient to use, though you cannot manage or modify any aspects of them. For small businesses and start-ups looking to launch their own app without getting into a level of detail their project does not require, PaaS is perfect.

IaaS, on the other hand, is suitable for **large-scale app launches** as it gives developers access to high-quality app dev services and allows users to tweak every aspect of their project, including its very building blocks.

Both services are also priced differently. Heroku costs $0.05 per hour, whereas AWS offers a starting plan for as little as $0.013 per hour. It is worth keeping in mind, however, that though both operate on a pay-as-you-go basis, Heroku does have the most powerful offering, with its most powerful dyno type providing 14GM of memory for €500 per month.

## What Is Heroku’s Advantage Over AWS?

What is Heroku’s most compelling advantage? **Simplicity** … and **speed**! Using Heroku Command Line, you can create a new server in just 10 seconds and use Git Push for deployment. The service also provides many add-ons you can utilize even if you do not know the basics of Unix administration. Perfect for beginners, Heroku constitutes an excellent alternative for those businesses who do not have a DevOps engineer on their team but still want to build an MVP app, deploy it, and test it. For any project where huge computing power is not essential, Heroku is a wonderful solution, especially if you want the ability to make quick changes and fixes based on customer reviews, for instance.

## What Is Heroku’s Downside Compared to AWS?

Though it is ideal for beginners, Heroku may be limiting if you ever find yourself requiring **automated scalability**. AWS is for those who need to do everything **on a larger scale** and to have full control over the infrastructure they use. If you do not mind – or even prefer to – dedicate ample time to the creation and development of your app and every new version of it going forward, the immense computing power AWS offers may be worth taking advantage of.

Both Heroku and AWS are excellent **cloud-based solutions**, but they do differ in some key respects. With a little foresight, you should be able to pick the right service for your organization. Look at the skill sets (DevOps) available to you and consider your short- and long-term business goals to decide where your priorities lie.

- [Get Strapi up and running in 3 minutes](https://strapi.io/documentation/v3.x/getting-started/quick-start.html)
- [Get access to a hosted Strapi with sample data](https://strapi.io/demo)
- [Discover Enterprise Edition](https://strapi.io/enterprise)

The Ecosystem section covers everything related to the world of Headless CMS and Strapi's place in it. 

Ecosystem

What is Heroku and How is it different from AWS

What Is Heroku and How Is It Different from AWS?

Long gone are the days when only those well versed in programming languages were able to even contemplate building a presence online. **CMS websites** have not only opened web design up to a much more diverse array of creators but allowed specialists to switch their focus, giving them more time to experiment and innovate.

![Screenshot 2020-10-20 at 16.14.45](/uploads/Screenshot_2020_10_20_at_16_14_45_ac2cf9b03f.png)

## What Is a CMS Website?

A CMS website is, as the name indicates, a website built using what is known as a [Content Management System](https://strapi.io/features) – or CMS – which provides a convenient framework to create content or modify it on the fly. What makes CMS different from more traditional web design solutions is that they feature a practical user interface through which content can be added or organized. Though older generations of content management systems may have been relatively restrictive, particularly in terms of layout, they now offer incredibly diverse options, usually in the form of themes. These let users manage their pages as they please without having to create HTML documents from scratch.

## What Are the Most Popular CMS?

Over half of all sites on the Internet are CMS websites, many of which are powered by **WordPress.** This content management system is known for its versatility and ease of use, with an immense array of plugins that provide functionalities most web designers find amply sufficient. Other options include **Drupal**and **Joomla**, both of which are considered more powerful but more complex, making them suitable for web design professionals. Even e-commerce websites can benefit from dedicated solutions such as Magento, Shopify, OpenCart, or Prestashop. Some beginner-friendly alternatives – for instance, Wix – boast fewer functionalities. They do, however, have the merit of being very approachable.

As for those who want no compromises, **Strapi **is regarded as a CMS of choice. From static websites to mobile applications, brand or [corporate websites](https://strapi.io/solutions/corporate-website-cms), editorial sites, e-commerce, and more, this **fully customizable open-source headless content management system** places personalization at the core of its offer. The intuitive interface is designed with comfort and flexibility in mind and caters to developers who need a dependable structure and more advanced functionalities.

![HP_meta_b32f546a40](/uploads/HP_meta_b32f546a40_546ca76170.png)

## Why Opt for a CMS Website?

In our fast-paced world, efficiency is at the heart of everything. Online, this dynamic is more emphasized, which is certainly why CMS websites are proving so popular. Back in the day, each small update would require altering the HTML, making it a challenging task for businesses to manage their own content. Using a CMS means even a complete layout overhaul is a breeze to achieve!

As for the content itself, adding images or videos can be done without mastering a single line of code. CMS users create new pages on the fly, publish blog posts that they can write and edit straight from the interface, arrange portfolios, manage their stocks by adding or removing products, all through simple drag and drop actions, or at the click of a button. And they do not have to work alone either, as a CMS website can be managed by several administrators and support an entire team of contributors with more or less advanced privileges.

From a development perspective, a CMS framework is an invitation to focus on fabulous design and amazing functionalities, since no time is wasted on handling the more trivial elements of the website. The content itself is safely stored on a database and is fully organizable in the form of convenient archives.

![Screenshot 2020-10-20 at 16.15.01](/uploads/Screenshot_2020_10_20_at_16_15_01_7e11fc10ab.png)

**Search Engine Optimisation** – also known as SEO – has become a pivotal aspect of website management. With content-based rankings still shaping search results as we speak, being able to produce and publish quality content easily is an immense advantage. In addition, using a CMS gives you access to powerful plugins that can make a world of difference. **Yoast**, for instance, gamifies the search engine optimization process by indicating your SEO score through a color code, the ultimate goal being green.

Finally, many CMS are **open source** by nature. Though this is not the case for all systems, opting for an open-source CMS lets you unleash your creative potential by building your very own themes and plugins. You can also alter existing ones to tweak them according to your liking. Even the frameworks themselves can be edited and extended, so long as your knowledge of the CMS in question, MySQL and PHP are sufficient.

Choosing a CMS website presents benefits that could not be overstated. Even though static websites still have some uses, businesses are finding content management systems more and more compelling. **Cheap, convenient, powerful, highly customizable, and constantly updated,** they offer a wide range of possibilities for those who want to give their audience an optimal viewing experience regardless of the device they use. They also provide you with all the room you need to keep on growing. CMS is a great way to make your website truly yours and to have it reflect something unique, creative, and beautiful.


Community Spotlight

What is a CMS Website and Why Should You Use One?

## When to Use GraphQL vs REST?

In the GraphQL vs REST battle, the latter is often cited as a point of reference. However, many advocates in favor of the more advanced technology GraphQL supposedly boasts. How do these two API design architectures really stack up against one another?

In this article, we will look at the differences and similarities between both solutions and compare their benefits and limitations. Let us try and determine which one truly surpasses the other or certain automation needs may call for one solution in particular.

## What is the Difference Between GraphQL vs REST?

The core difference between GraphQL and [REST API](https://strapi.io/documentation/v3.x/content-api/api-endpoints.html) is that the former is a specification, a query language, as well as a set of tools that utilizes HTTP to operate over a single endpoint. REST, on the other hand, serves as an architectural concept used to implement web services. Recently, GraphQL has been employed to optimize the performance and flexibility of existing APIs, whereas REST has often been the option of choice to create new ones. 

## What is REST?

REST operates on the logic that everything is a resource identified by a URL. In the REST paradigm, the textual representations of web resources can be manipulated by RESTful web service systems. To that end, the architecture relies on a predefined set of stateless operations such as POST, PUT, DELETE, GET, etc. For instance, one would put a GET request through to the resource’s URL. The response would then arrive in a JSON format, or in any format, the API calls for.

The main benefit of REST is that it is scalable and decouples client and server, allowing developers to work on products and applications independently. Compatible with a wide range of formats, it can meet a variety of needs.

A key issue, however, is that multiple requests must be sent in order to access and combine data from different endpoints. In addition, developers often have to deal with over-fetching (information downloaded in excess of what the application needs) and under-fetching (not enough information received by the client, which then has to make several requests.

## What is GraphQL ?

The GraphQL vs REST debate stems from the fact that GraphQL is ruled by the same constraints as REST APIs. What sets it apart, however, is that the data is organized in a single graph-type interface. [The GraphQL schema](https://strapi.io/documentation/v3.x/getting-started/graphql.html) is used to define objects in the form of nodes, whose relationships are represented by edges within the graph. A resolver then backs up the object and accesses the data on the server. The implication is that the GraphQL query language gives the option to tailor requests to some very particular requirements.

This architecture solves any performance issues related to overfetching by allowing the user to receive only the data they specifically requested. In addition, several entities can be combined into a single query. GraphQL has the merit of accommodating client-side changes without impacting the server by making it possible to have rapid product iterations on the front-end. As for the back-end, developers who use GraphQL gain significant insight into any data request and into how the available data is being used. Thanks to GraphQL, developers can improve API performance by deprecating disused fields, since every client can specify the exact information they require. The client is directly informed as to how it can access the data in question and, since its structure is known both by the front-end and the back-end teams, they are not co-dependent.

Yet, because this architecture doesn’t follow HTTP caching specifications and uses a single endpoint, network-level caching is compromised. With that said, caching does remain possible thanks to several workarounds. For instance, identifiers can be derived from globally unique IDs. Caching can be done at the client level, at the individual resolver level, at the whole response level, etc. Finally, because it adds a level of complexity, GraphQL isn’t always the best answer to some simple API needs.

## Why Use GraphQL vs REST?

The main advantage of GraphQL vs REST is its query language, which allows it to tailor the request to the developer’s needs, be it for a set of objects or for specific fields an entity contains. This gives them the ability to gather information from one particular endpoint without having to receive a whole set of data along with it. GraphQL can look for precise information and limit its efforts – and therefore the amount of processing it requires – to the bare minimum, making it worthwhile.

When Should I Use REST API?

However, the GraphQL vs REST question does remain valid because GraphQL cannot match the practicality of REST. This is the reason why, in many cases, it is still considered the industry standard when it comes to deploying APIs. It is also characterized by a more significant amount of tooling, which GraphQL simply does not have … yet!

The bottom line is that for anyone serious about creating automation, wondering whether to favor GraphQL vs REST is perfectly warranted. While the learning curve is undeniable and GraphQL is not as established as REST, being able to sort through the data before it is even fetched has great advantages. Without having to process large amounts of data, the performance also increases when using GraphQL, which can translate into huge wins once at scale.           

This is why Strapi chooses to offer both options. Whether you wish to build your content API using RESTful or GraphQL, Strapi strives to bring you the most customizable experience in content management solutions. 

[Install Strapi now](https://strapi.io/) and start creating flexible data structures, writing, editing, and managing any content types, and building the apps you want, with complete freedom. 


Configuring Strapi and MySQL

GraphQL vs REST: How to make the right choice?