We have a Google Cloud Endpoints backend written in java. We generate the client library to use in other Java applications with the command
gradlew endpointsClientLibs
Is it possible to generate a NodeJS client library from the same Java backend. We winsh to write some of out applications in NodeJS
This is not currently possible. We (the Endpoints team) are aware that users would like more client language options.
I use Google's Discovery API to generate a client library which is based on the open API spec file in Python for my cloud endpoints api. I assume the same can be done for node.js.
Google's node.js Client Library - https://github.com/googleapis/google-api-nodejs-client#google-apis
Google's Discovery API - https://developers.google.com/discovery/v1/using
Related
I'm researching about building a custom server for sending push notifications to clients Webapps (No android or iOS phones). What would be a reliable and scalable stack for building this service? Preferably using a microservice architecture. Thanks.
P.S. I already tried third party services such as FCM, OneSignal, but most of them don't offer a custom domain option.
You can use spring-boot framework for this, which provides easy configuration to connect with firebase using firebase SDK or API's.
Download firebase admin SDK : https://console.firebase.google.com/
Create spring boot application : https://start.spring.io/
Use private key JSON file to connect with firebase using SDK.
Expose REST end points to send FCM notifications.
For those looking for a current answer (April 2021), you cannot use your own push service because it is tightly coupled with each browser push API implementation:
But notice that we can't push notifications from our server directly to the user's browser. Instead, only certain servers that browser development companies (like Google, Mozilla, etc.) specifically choose will be able to push notifications to a given browser.
Link:https://blog.angular-university.io/angular-push-notifications/
I'm looking for a tool what I can use for generate an initial web application.
Previously I used JHipster for my Applications, which uses Java Spring on server side, but currently I don't want to maintain a Spring backend only a NodeJs.
Requirements:
using Angular as frontend
using NodeJS as backend
using Firebase for (authentication, collection and data storage)
pre built Authentication mechanism (including user register and login)
Do you have any suggestion?
Or how can I speed up these initial steps?
you could use https://github.com/jhipster/generator-jhipster-nodejs it does not use Firebase
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
We are looking at using Azure for the backend for our native Android application. The application will have user accounts along with product information and order history information. The idea is to manage the user, product, and order information in the Azure backend.
Could you help confirm if my understanding is correct on the following:
There are three components involved: native Android app on client side, Node.js app on the server side, and Azure Storage.
The Node.js app on the server side is where for example get/set user/product/order API calls are implemented
Backend implementation is offered via Node.js or .NET via SDK, but for other implementations can also be done via REST calls to Azure
storage
The data flow involved is: Android app communicates to Node.js app via REST API, while Node.js app communicates to Azure Storage via SDK
(or REST API).
If you could help confirm these, it would be greatly appreciated
Mobile Apps is the mobile-backend-as-a-service which have the API consisted of standard HTTP verbs (GET, POST, etc). Every HTTP verb has the script associated with that that can be written using C#/Node.js on the backend side. That code is being executed every time that HTTP verb is "executed" by the client. Client can have whatever he wants in terms of language/platform.
There are three components involved: native Android app on client side, Node.js >app on the server side, and Azure Storage.
It depends on what you are using. If Mobile Apps, then there is SQL Azure. If not - then you can use Storage, SQL or whatever you need.
The Node.js app on the server side is where for example get/set >user/product/order API calls are implemented
Node.js in Mobile Apps are implemented as the scripts that are executed when there is some HTTP method invoked by the client. For example, you are able to implement the PUSH notification if client invokes POST HTTP method and insert some entity into the storage backend using Mobile Apps.
Backend implementation is offered via Node.js or .NET via SDK, but for other >implementations can also be done via REST calls to Azure storage
Yes. But again, if you mean Mobile Apps (i think you do), then it is SQL Azure, and here you can use SQL Server Management Studio, Visual Studio or something else to manage the SQL Azure DB. Or use REST API.
The data flow involved is: Android app communicates to Node.js app via REST API, >while Node.js app communicates to Azure Storage via SDK (or REST API).
Node.js backend communicates with the storage backend using modules that you can add (for example, SendGrid to send SMS or store the blobs in the Storage) and some underlying technologies and adapters.
I simply am wondering if the only way to have any sort of spotify application be web-based, as opposed to app-based, would be to have it as a Spotify app within the Spotify application or if it's possible to have it standalone.
It sounds like you're getting confused between our APIs.
Spotify Apps is a platform inside our Spotify client. You write them using HTML5/JavaScript. They're run locally, but you can have it talk to a backend service if you wish.
Spotify's Web API provides HTTP REST services for search and metadata lookup.
libSpotify is for standalone native applications. You can have that application host a web service — there are Ruby bindings, for instance — but there are a few Terms of Service you need to be aware of concerning logging in as a user from your own service. You can find the ToS on http://developer.spotify.com.