These are chat archives for reactioncommerce/reaction

17th
Dec 2018
Purshottam Sharma
@impurshottam
Dec 17 2018 03:45
Hello Guys, I was comparing magento vs node.js framework for my next project and i accidently reached here. Should i go for magento or try node.js? Things that i am looking are pricing, performance, scalebility, learning cure and the most is community support.
Chetan Yadav
@imchetanyadav
Dec 17 2018 07:52
Hey, is it possible to move signin/signup form to nextjs storefront and pass field values to meteor and perform authentication there?
Loan Laux
@loan-laux
Dec 17 2018 11:04
@imchetanyadav No, because of the way OAuth is implemented in Reaction this is currently not possible. At least not without a lot of modifications which would make the platform way less secure. See the recent discussion on this topic here: reactioncommerce/reaction#4852.
Loan Laux
@loan-laux
Dec 17 2018 11:22

@impurshottam Hi there! I would highly recommend Reaction, especially now that version 2.x is starting to reach a certain level of stability. The Next.js + GraphQL storefront makes for an awesome developer experience and very quick loading times for end-users since it's got SSR. Overall performance is top notch and it would be very hard to get anywhere close with any other solution on the market.

On pricing, well... Reaction Commerce is open-source, so you won't have to pay for any licence. You will pay for hosting though, but considering that you'd host Magento on a cloud environment anyways, we'd be roughly in the same ballpark.

As far as scalability goes, Reaction has always been focused on that since day 1, which is why it plays very well with Docker. Deploying a project based on the new micro-service architecture, you would ideally use a public container cloud such as AWS ECS. This setup makes it very easy to scale Reaction and obtain a virtually bulletproof website. This is obviously doable on a private cloud as well with technologies like Kubernetes.

When it comes to the learning curve, Reaction is in an interesting state right now. Since it's moving away from Meteor to focus on technologies like pure Node and GraphQL, the codebase is currently a mix of both living in harmony. As the platform evolves, we see less and less Meteor code which makes for more consistency. Regardless, starting a Reaction Commerce project right now means your developers will sometimes need to tinker a bit with the Meteor parts. Luckily, Meteor is really easy to wrap your head around. An experienced Node.js developer shouldn't run into major problems trying to work with this code.

To answer your last point, the community around Reaction is very active. RC themselves are pretty attentive to what the community says, which is great and definitely not the case everywhere.

However, depending on the scale of the project, there's a chance you may want to get help from an experienced consultant to guide you and your team through your first steps with Reaction. Implementing best practices, writing futureproof code and understanding the most complex parts like tax/shipping is definitely easier when you have someone who's experienced by your side!