You are here:Home1/Insights2/Frontastic explains: Cloud native
Frontastic explains: Cloud native
In the fast-changing digital world, it’s hard to keep up with upcoming technologies, techniques, and software solutions. We don’t want marketers, agencies, or developers to lose track and want to provide the knowledge of our highly experienced team to everyone interested.
In our series “Frontastic explains,” our Lead Editor Catherine sums up the meaning and the impact of the biggest buzzwords of the digital world.
Today’s topic is cloud native.
Cloud native is a way of creating and updating websites or applications specifically using cloud computing. That means utilizing the shared pool of computer resources. Then quickly and easily configure them to your needs with minimal effort.
But wait, what’s the cloud?
The cloud is a global network of servers where data can be stored and accessed over the internet rather than on a physical server or the hard drive of a computer. It’s about removing the hardware you can physically touch. The servers are still there, but now they’re spread across the whole world as a network, and they’re accessed remotely.
If you have an on-premise server, you’re responsible for hosting and keeping your infrastructure up-to-date and running, and it has limited space. If you use a cloud server, you rent a piece of the server network, and you only pay for what you use. You don’t have to worry about the space on your server, you can increase or decrease the amount of servers you use to suit your needs. And as they’re looked after by specialists, you don’t have to worry about safety, security, or any other issues they have, for that matter.
More agility and less complexity thanks to cloud computing
The cloud model of computing makes IT more simple. It’s also reliable, stable, and easy to use. Since it’s all available on the cloud, you can access your systems when you want, easily and from anywhere.
So being cloud native means that you only utilize this way of computing to create and update your website. It saves you time, money, and resources. And it also gives a better experience to your users.
Cloud native versus on premise: What are the pros and cons
Especially in the commerce world, there are still some reasons to choose a monolithic approach and go with the proven yet old-school on-premise way.
But the list of pros of cloud native applications speaks for itself. Not without reason, the current commerce industry sees a huge change from on-premise to cloud.
Lower operational costs
Fast time to market
Access to newest technologies without a big investment of time or money
High safety standards and close to zero outage times
Companies stay ahead of their competition
Dependence on the chosen cloud operator (data safety, vendor lock-in, and so on)
Limited individualization options
flaschenpost.ch customer story: From on premise to cloud
Switzerland’s largest online wine retailer is building the future of its digital business with Frontastic and commercetools as the cornerstones. The decision brings speed and agility — and guarantees the best possible shopping experience for its customers.
The team quickly noticed: they were no longer getting anywhere with the existing Magento-based store. “The monolithic structure of Magento has been customized again and again over the years. This made it increasingly complicated, lengthy, and therefore very expensive to develop new features,” explains flaschenpost CTO Johannes Klaiber. Management quickly decided that the future consisted of a headless architecture that created independence between the frontend and backend — and chose the combination of commercetools as the backend and Frontastic as the Composable Frontend Platform.
“This gives us a faster time to market because it’s a modern technology that fits better with our skillset and developments,” Klaiber explains. At the same time, he says, the setup enables the company to build a more agile organizational structure. “Our goal is to create product teams that can independently drive their own projects,” says the CTO. One team could then take care of the store, for example, while another takes care of building a subscription model. And no one would have to take into account when the other changes or installs anything in the system.
In our architecture blog series, we'll look at each part of the Frontastic architecture, how it works, and what you can do with it. In this post, we'll focus on the developer tooling that comes with Frontastic.