im developing a web-app. and one of my requirements is a page in which multiple users can share the same state. Kinda like a game room that all users see the same game and when one user interacts with an item everybody can see the progress. Ive got this covered with firebase and firestore. Now i want for all the users to see each others cursors. Since this requires alot of real-time updates, using firestore would be too slow and too pricy. Can anyone suggest a solution? Maybe some form of SaaS that can provide real time updates for a resonable price?
Gave it a go with firestore but that is too slow and pricy
Related
I am far for being an expert in web development or any app development in general but i have the basics. I want to develop a simple microsoft Teams app for my organisation in order to do HR management. I want to use MongoDB to store the data. However I've spent quite a lot of time on trying to figure out how does the toolkit works. How can I create an teams application in teams using a mongoDB database. Which language should I use, React JS?
If you have any useful links i'll take them.
Thanks for your time guys :)
My company (which does Tutoring services) recently transitioned to Square for their Appointments and POS and I am trying to automate certain tasks. I wanted to know if there was a way to create "Open Tickets" for transactions through the Connect API.
I went through the documentation and couldn't find anything that refers to "tickets". I checked the seller community but wasn't satisfied with the answer from Square since they seemed to not understand what "Tickets" meant. I have provided more details at the end of this post in case someone wasn't sure about "Tickets" here as well.
I believe currently Tickets are only available through the Square POS app (Android/iOS) and not on the Web Dashboard. I would like to be pointed in the right direction in terms of what I might need to look at in order to get access to automatic ticket creation.
For more details, please read on.
In order to clarify what I mean by "tickets", here is Square's page regarding "Open Tickets". They are basically a way to create and save transaction info ahead of time so customers can be charged quicker. The way we use "Open Tickets" is we create tickets for Tutoring sessions every day in the morning and when a customer shows up, all they have to do is look up their ticket and pay. We do this since we expect a lot of traffic every day and we want to streamline the process as much as possible.
Therefore, our admin staff ends up creating 80-100 tickets manually every day! I wanted to know if there was a way to automate this. I already have a running Google Sheets with all appointments data that would be needed in order to create a ticket. I just need to find a way to communicate with ticket creation.
I apologize if this is a long post. I tried to be concise but thorough. Please let me know if there is any detail that I missed. I appreciate any help!
Unfortunately, Open Tickets isn’t currently available for Square’s API. Square's API is only able to track completed transactions at this time.
We are constantly improving the product based on feedback like this, so I’ll be sure to share your thoughts with the API team.
I'm currently working on a app, which has been build by another company already.
They build it on Appcelerator ACS (arrowDB) but when testing the queries are just too slow, where the same query on Parse.com is twice as fast.
So i'm trying to check how much work it is to put the existing database to parse.com but remain a functional app.
It's including users and quite a lot of custom objects and linkings.
It there anyone who moved from ACS to Parse?
If so, how was your process and are there things worth mentioning?
I am getting to launch a new app which is network based. Right now I do not have it scaled very large (I only have one server running). Is there anyway through Google Play that I can restrict the downloads to a couple of hundred people until I can purchase the scalability I need for my app? I want to have a maximum of a couple hundred people download the app a month so that I can scale accordingly. Is there anyway to do this besides removing it from the store every time I get too many downloads?
You could utilize Google Play Alpha/Beta testing which allows you to invite people to either a Google Group or Google+ Community and only those people can download your application from Google Play. That way you could cut off membership once you've hit a certain number of people (note that if you are using a Google+ Community, you want to make sure you make it Public - Moderator approval to join or Private) and then restart once you've scaled up.
However, if you are doing a traditional production publish of your app then there is no way to limit the number of people downloading your application.
I am looking for some recommendations on a good data store for activity feeds. The goal is to have a Twitter/Facebook type feed log consisting of various activities users can do throughout our website. The "wall" or "feed" would updated via AJAX showing what the users of the website are currently doing. It will be written to often and then the most recent will be displayed on the site.
(e.g. John Smith recommended Jane Smith's article 2 seconds ago)
We currently are storing the feeds in MySQL but performance has been poor and I'm concerned with hindering performance throughout the rest of the website if we are constantly hitting the database to grab the most recent user activity as well as writing the feeds.
Any recommendations would be greatly appreciated!
Make use of the best caching solutions like memcache to increase performance. Other than scaling, there are no performance-increasing possibilities for an activity feed.
I would vote for using http://redis.io/ or http://www.mongodb.org/ as an alternative to MySQL for short-term, almost live activity feeds across a site. And a cron job to dump history of activities into MySQL for record keeping.
A look at tumblr's or twitters architectures can push you to the right direction as well.
You should take the microservices approach to separate between the datastore that stores the users' actions to the one that store the actual data.
Pub/Sub is the right approach to handle the big stream of users' actions.
Use Kafka or Google Pub/Sub cloud service for a scalable data pipeline. They can take the load with its scalable architecture.
Independently consume the messages from Kafka to some database such as MySQL or Google BigQuery for analytics purposes you must have.