I usually develop web apps with MEAN but I came to work for a business that uses Bigcommerce. I want to know if I can incorporate node.js applications into bigcommerce and if so, how?
Our API is language-agnostic, so you can use Node.js or any other language to integrate with a store. Here's a link to a community-contributed SDK that may help you get started:
https://github.com/getconversio/node-bigcommerce
This SDK provides methods for authenticating and making requests against the BigCommerce API. We are a SaaS platform, so any code that you write would be hosted on your own server. You can check out our developer documentation for more resources: https://developer.bigcommerce.com
Related
We have been using Azure Easy API using Node.js for some of the mobile apps. Given the fact that the mobile apps stay in different versions, we need to have different versions of the same API available. In such a case, how do we carry out the versioning? Is there any azure documentation that someone can point to? thanks in advance.
There is no documentation on versioning for Azure Mobile Apps. Internally, we use the ZUMO-API-VERSION to switch between protocols. If you are using EasyAPI, then that is designed for the most simple cases - versioning of your API is not supported.
Instead of using EasyAPI, the site underneath is just a Node.js application. Download it (via Kudu), check it into source code, and use regular old Express routing for your API. You can then version it any which way you like.
If you need further information on versioning WebAPIs, I recommend Designing Evolvable Web APIs with ASP.NET - it's on ASP.NET, but covers a lot of the required semantics for versioning within it.
I built a web application using react and node , and also i want to build a mobile app , so i'm trying to build REST API to manage the database . I heard about the Azure API management and trying to using it but couldn't find any tutorial that relevant with javascript
Does Anyone know good tutorial to refer??
Azure API Management is not intended to create API, it is intended to act as a proxy, to harden your API against attacks from outside. You should be using WebApp or ApiApp to create your API.
I assume that you want to build Mobile App back-end on Azure with node.js SDK.
About how to use the Azure Mobile Apps Node.js SDK, you could refer to the official documentation here: https://learn.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-node-backend-how-to-use-server-sdk.
Also, you could take the following complete series tutorial on the Node.js SDK as reference: https://shellmonger.com/30-days-of-azure-mobile-apps-the-table-of-contents/.
Any further concern or my misunderstanding, please feel free to let me know.
ejabberd can be extended through an API. How does it work with ejabberd SaaS ?
Can I deploy a module I have developed ? Can I deploy a contributed module ?
ejabberd SaaS is designed to run a standard single platform that is identical for all customers.
As such it does not allow running custom modules (It would be a security risk).
However, it is design to offer API the users can implement to integrate with user backend as needed. There is a simple set of ReST endpoint to implement to be compliant and provide user authentication, contact list or message archive (more are on the way).
is there any way to publish my API in azure mobile service API instead of using its own. I want just to know it, because assume I have a backup server in amazon and as you know I don't have access to azure sdk in there and it means technically I cant use the API anywhere outside the azure.
Azure mobile services is actually based on the .Net web api in their C# flavor and on node.js on the Javascript side. You could surely write an API using those technology and have the same behavior. You will gain the fact of being more portable, however you will lose some of the preconfigured stuff from Mobile services.
If you are using .NET, please check this to see how to build a Web api! http://www.asp.net/web-api.
If you are using Javascript, here is where you should start : https://nodejs.org/
Both tech are quite easy to learn and super powerfull, have fun! When your API is built, you could just publish them as an azure Web APP (http://azure.microsoft.com/en-us/services/app-service/web/) or an Azure API (https://azure.microsoft.com/en-us/services/app-service/api/) instead of the mobile App
Hope it helps, if you have more questions, please ask!
You can create and publish your own custom APIs in azure mobile service. You could even access in via azure mobile service sdk in client by using "InvokeApiAsync<>()" method.
https://msdn.microsoft.com/en-us/library/windows/apps/xaml/dn614130.aspx
If you want to access the api via fidder/httpclient than AZM SDK, pass the mobile service key in HTTP header as Name:'x-zumo-application' value:'application key from portal'
I have a WebAPI back-end for a mobile, and want to host it in Azure.
I am having a hard time figuring out the real differences between AMS and Websites.
All the articles I read about the subject talks about changes and benefits in general, and I want to understand specifically which new features AMS provides, and the benefits of hosting in AMS.
Authentication
In AMS I see the "IDENTITY" tab in azure portal. From what I understand, those 3rd party configs allow me to authenticate my users easily with google,FB etc. But this is just making the process more convenient and configurable via UI. In Websites, I can achieve the same functionality pretty easily using code from ASPNet.Identity and OWIN libraris.
Push Notifications
Again looking at AMS in the "PUSH" tab, I can see two mechanisms. The Notification Hub and 3rd party section.
The Notification Hub is nothing special to AMS, and I can get the exact same functionality when hosting in Websites.
The 3rd party section allows me to configure credentials to push services from Apple and Google (APNS,GCM...) and together with libraries in AMS namespace I can easily write code to communicate with those services.
But When hosting in Websites, in my back-end I can use open source libraries. For example, Moon-APNS to talk to APNS.
Scale
As far as I understand, both Websites and AMS allows the same scale functionality (One calls it Units and the other Instances).
Are there any big differences I missed?
Are any of the claims I made are incorrect?
It would be great if anyone could shed some light on the matter, specifically addressing all the 3 issues (Auth,Push,Scale).
That's a question I often get when I present Mobile Services at user group events.
For a .NET developer, there's nothing really special about Mobile Services since everything it offers, you can do it with a Website.
Mobile Services really shines for non .NET developers since you can have a complete mobile backend by writing scripts running on Node and Mobile Services abstract all the database and REST complexity.
I will likely get downvoted since I'll express a personal opinion but anyways: I see no obvious reasons for using Mobile Services if you're coding a .NET backend.
I think you are exactly the target customer for Azure Mobile Apps. You will get all of the power of having your own Azure Website (now rebranded as Azure Web App), with the additional convenience and client libraries of Mobile Services.
One feature of the client library that you may not have noticed is the cross-platform offline data sync capability. That's usually hard to build on your own, and we have an implementation that's conceptually consistent across all client platforms. (Plus, if you use Xamarin, you can share code between your client implementations.)
To be clear: Azure Mobile Services is NOT deprecated, and will not be until long after GA (general availability) of Azure Mobile Apps. Azure Mobile Apps is currently in preview.
The other big benefit of Mobile Services that you haven't mentioned is the client libraries for Android, iOS, Xamarin, and Cordova. If you already have a REST client library in your app and don't need to worry about multiple client platforms, then Azure Web Sites sound like a good way for you to go.
AMS by itself is built on top of Azure Websites. So you can actually implement everything in an Azure website that is available in AMS.
However, the good thing about AMS is that it allows you to quickly build the backend for a mobile app with CRUD operations, authentication/authorization and also provides client side libraries for different type of clients e.g., HTML, C#, etc. so we don't have to manually make the HTTP calls.
If you have need to implement the above functionality in Web API, it is quite an effort. Isn't it?