Alternatives to Xano

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

I use Socket.IO because the application has 2 frontend clients, which need to communicate in real-time. The backend-server handles the communication between these two clients via websockets. Socket.io is very easy to set up in Node.js and ExpressJS.

In the research project, the 1st client shows panoramic videos in a so called cave system (it is the VR setup of our research lab, which consists of three big screens, which are specially arranged, so the user experience the videos more immersive), the 2nd client controls the videos/locations of the 1st client.

We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.

Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

Recently we finished long research on chat tool for our students and mentors. In the end we picked Mattermost Team Edition as the cheapest and most feature complete option. We did consider building everything from scratch and use something like Pusher or Twilio on a backend, but then we would have to implement all the desktop and mobile clients and all the features oursevles. Mattermost gave us flexible API, lots of built in or easy to install integrations and future-proof feature set. We are still integrating it with our main platform but so far the team, existing mentors and students are very happy.

We need to interact from several different Web applications (remote) to a client-side application (.exe in .NET Framework, Windows.Console under our controlled environment). From the web applications, we need to send and receive data and invoke methods to client-side .exe on javascript events like users onclick. SignalR is one of the .Net alternatives to do that, but it adds overhead for what we need. Is it better to add SignalR at both client-side application and remote web application, or use gRPC as it sounds lightest and is multilingual?

SignalR or gRPC are always sending and receiving data on the client-side (from browser to .exe and back to browser). And web application is used for graphical visualization of data to the user. There is no need for local .exe to send or interact with remote web API. Which architecture or framework do you suggest to use in this case?

Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

I want to use NATS for my IoT Platform and replace it instead of the MQTT broker. is there any preferred added value to do that?

Hello,

I'm in the midst of reviewing an old CRUD SAAS I have running on Angular 7 with a MariaDB backend and Laravel PHP. Presently is hosted on a couple of Linode servers- and really feeling the weight, especially with the looming need to upgrade to A15 and meet the pace and scalability occurring (for context, the SAAS turns in over 24k USD monthly in subscriptions- so I have concerns around the impact of a new stack on existing clients). Additionally, I manage a Kotlin and Swift codebase for appdev.

I'm looking at moving towards Flutter for a singular codebase, and something serverless but still relational- like Supabase. In the past, I ran my own Auth services- but it was a ton of work to setup and maintain, so looking at using Firebase for Auth services (I know Supabase has Auth as well, but I wonder if it's as reliable and frequently maintained as Firebase?) Supabase has a FlutterSDK as well which makes things much simpler. Planning on maintaining microservices like Stripe etc for functional aspects.

I would love some insight from those who have done a tech stack transition, what should I be aware of- those who have produced in Flutter or a similar stack, what am I walking into without knowing?