Skip to main content
Magento

Return to Question

Add PWA Studio official Magento 2 tools
Source Link
Franck Garnier
Franck Garnier
  • 2.9k
  • 1
  • 18
  • 35

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

EDIT : A nice open source project in order to use Magento 2 as a headless E-commerce with VueJS PWA : https://github.com/DivanteLtd/vue-storefront

EDIT : The official Magento 2 PWA tools based on React : https://github.com/magento-research/pwa-studio

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

EDIT : A nice open source project in order to use Magento 2 as a headless E-commerce with VueJS PWA : https://github.com/DivanteLtd/vue-storefront

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

EDIT : A nice open source project in order to use Magento 2 as a headless E-commerce with VueJS PWA : https://github.com/DivanteLtd/vue-storefront

EDIT : The official Magento 2 PWA tools based on React : https://github.com/magento-research/pwa-studio

added 153 characters in body
Source Link
Franck Garnier
Franck Garnier
  • 2.9k
  • 1
  • 18
  • 35

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

EDIT : A nice open source project in order to use Magento 2 as a headless E-commerce with VueJS PWA : https://github.com/DivanteLtd/vue-storefront

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

EDIT : A nice open source project in order to use Magento 2 as a headless E-commerce with VueJS PWA : https://github.com/DivanteLtd/vue-storefront

Add API bootstrap example
Source Link
Franck Garnier
Franck Garnier
  • 2.9k
  • 1
  • 18
  • 35

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

I want to know if there are some best practices to use Magento 2 as a headless E-commerce solution.

A typical E-commerce in 2017 is to have an omni-channel solution which includes

  • E-commerce
  • CMS
  • Multiplatform
  • Tier system integration (ERP, ...)

I want to know how involve Magento 2 API with this kind of solution.

My approach:

  • Use a different frontend framework (such as angular) for desktop/mobile webapp and mobile app

  • Only use Magento 2 API in order to retrieve or interact with E-commerce data/action

  • Only use CMS API in order to retrieve CMS data.

Pro: Only API's, omnichannel

Cons: Limitation for performance/features/formatting

Some questions for this approach :

  • Who is responsible for formatting data, for example prices. Magento API and frontend framework?
  • Who is responsible for resizing product images and cache them? Because in the native Magento 2 API there is no resize or cache system.
  • Do I need to create new custom isolated API or extend native for future upgrade purpose?
  • Do you recommend to use an extra layer in order to combine CMS and Magento API?

I appreciate you to share your return in experience.

Moreover, I found this approach: http://fbrnc.net/blog/2015/10/super-scaling-magento

Usefull links :

EDIT :

I found a good bootstrap in order to create your own cache logic for your Magento 2 API : https://github.com/magespecialist/m2-MSP_APIEnhancer

Add headless approach links
Source Link
Franck Garnier
Franck Garnier
  • 2.9k
  • 1
  • 18
  • 35
edited tags
Link
Teja Bhagavan Kollepara
Teja Bhagavan Kollepara
  • 3.8k
  • 5
  • 33
  • 69
added 45 characters in body
Source Link
Franck Garnier
Franck Garnier
  • 2.9k
  • 1
  • 18
  • 35
added 163 characters in body
Source Link
Franck Garnier
Franck Garnier
  • 2.9k
  • 1
  • 18
  • 35
Notice removed Draw attention by Franck Garnier
Bounty Ended with Sinisa Nedeljkovic's answer chosen by Franck Garnier
Notice added Draw attention by Franck Garnier
Bounty Started worth 50 reputation by Franck Garnier
Tweeted twitter.com/StackMagento/status/834927435221250048
grammar corrections
Source Link
edit approved Feb 23, 2017 at 10:21
Glorfindel
edit approved Feb 23, 2017 at 10:21
Glorfindel
  • 358
  • 1
  • 7
  • 13
Source Link
Franck Garnier
Franck Garnier
  • 2.9k
  • 1
  • 18
  • 35