I would like to know what are my options and what are the best practices for apps that update themeselves regurarly though internet connection.
Example app: Livescore app which updates itself with the latest match results.
What are the best "free" ways to do this? (a server might cost me money for this?).
So far I found a tutorial which uses google sheets. Do you recommend it?
My app is going to update itself once a day.
Thanks in advance!
Firebase. Upgrading is not necessary, unless you're looking for some special features / capacity. Pubnub. Great for real-time data transfer. Free version is up to 1M messages. I would search online for other services as well, if I were you.
Related
I'm continuing with the Java programming of an Android app. Currently I use a local mysql server controlled with phpmyadmin. Having arrived at a good point, I was starting to look for a good hosting site. However, on the internet they speak mostly of the best for some services like wordpress. For this reason, do you have any advice on mysql and Android databases? I was inclined to start with one for free (I found 000webhost for example) but on the internet those that are free are not recommended. At a low price there are several such as hostinger, keliweb and many others. Should I start directly with a paid one? Thank you so much for the answers
Well, it's a good move to make. I have used iPage for about 5 years now and I've never had any issue with them. I also offer hosting with unlimited mysql database, domain, emails and bandwidth as a re-seller agent for iPage at $75/year with no hidden charges. I'm on Twitter
Well if your project is not large scale then it'll be good to go with 000webhost, it offers quiet nice service for free.
Only problem with 000webhost is that you need to use filezilla for better files uploading.
And if you are really looking for paid hosting then go for 1&1 IONOS.
They'll only charge 12$ for first year which will give you a good idea whether you really need a paid hosting or not.
I'm starting a team of 2 to develop a chat server (both of us are college students), we made some research and found that netty is the most suitable for this kind of concurrent based app.
we never had any experience in developing server side application in java, this is our first time to tackle this kind of project and I just need the right direction for us to build this server the right way.
Our goal is to build something like, whatsapp, kik messenger, Line or weChat.
The real question is, how to make our netty app scalable? do we need to use redis for data persistent? do we need to use mysql for saving relationship or nosql database like mongodb?
Hope someone could guide us.
You could have a look at the documentation if you don't have done yet:
SecureChat example
Netty User Guide
The scalability is a complex answear. One could think of making your application multi-servers able (horizontal scalability), but then it really depend on how your information/context/session are available/updated...
You could think of course to use some Redis for data persistency.
On database usage, it mainly depends on how your data are and if you need relationship using SQL language or if your application can do it for you (to be clear, do you want the database making for you the join parts in your SQL command, or do you want to use the application doing that?). Also it depends on the amount of data (1 millions, 1 billions, ?) and the amount of connections too.
So all is your choice...
Then you can come back with some issues you've got.
I'm not sure where to ask this so please suggest if I should move this to another stackexchange site
What technologie(s) are sites such as www.jsfiddle.net using in order to store data in the cloud ? Specifically the ability to store a code snippet and then retrieve it later via a URL. Is there a public generic API available for this functionality ?
I've researched cloud offerings such as https://developers.google.com/appengine/docs/java/googlestorage/ but since jsfiddle is free I doubt it is using such a service ?
Via the jsFiddle about page:
jsFiddle’s hosting is kindly provided by DigitalOcean.
There is no such thing as a free lunch: someone has to pay for storage. In this case, it's paid for by a third party, not by jsFiddle developers.
As to what they are using to store their data, it's unclear (though you can ask the developers: their names and websites are listed on that page), but the choice will basically be one of the following:
run a distributed file system on VMs rented from a cloud provider, or
use a managed solution, such as Google Cloud Storage that you pointed to, with an API
Either way, you will incur some costs.
I'm well aware of how I can communicate with an outside server using Android. Currently I'm using the relatively new AppEngine Connected Android project to do it, and everything works fairly well. The only thing that I'm concerned with is handling downtime for the server (if at all) and internet loss on the client side.
With that in mind, I have the following questions on an implementation:
What is the standard technique for caching values in a SQLite Database for Android while still trying to constantly receive data from the web-application.
How can I be sure that I have the most up-to-date information when that information is available.
How would I wrap up this logic (of determining which one to pull from and whether or not the data is recent) into a ContentProvider?
Is caching the data even that good of an idea? Or should I simply assume that if the user isn't connected to the internet, then the information isn't readily available.
Good news! There's a android construct built just for doing this kind of stuff, its called a SyncAdapter. This is how all the google apps do database syncing. Plus there's a great google IO video all about using it! It's actually one of my favorites. It gives you a nice really high level overview of how to go about keeping remote resources synced with your server using something called REST.
We have a website that is getting over 1m hits a day.
The site is running off an old architecture (Struts Tomcat Hibenate MySQl) with no real scope for scalability.
Now that we are expanding further I am looking for a modern (not too bleeding edge please) web architecture.
My first thoughts were to use Google App Engine - but I'm not sure that is open enough.
Our developers are all Java so it would need to be something they could pick up easily.
Ideally I'd like to run the same way as DIGG, Twitter, Amazon etc.
If you know how they do it - or have a suggestion I'd be very interested to know.
Unless you've got major bottlenecks baked into the design, then hardware is almost always going to be the best way to scale.
By 'best' I mean
cheapest
quickest
best performance increase
guaranteed results
It sounds like your current setup is having problems? Can you give any information on what kind of problems you have?
Edit: Can you give info on your current hardware setup? How many web servers (presumably running Apache?), how many app servers, how many DB servers?
I'd exhaust all possibility for "no real scope for scalability" before I rewrote my app. It might just mean that you can only scale horizontally by throwing more hardware and clustering at the problem.
Google App Engine will mean JPA instead of Hibernate and MySQL, because I believe they use BigTable in the back.
Hire a team or even better a company which has an experience in building scalable solutions. Promote current developers in Business Analysts and make them help the scalable solutions specialists with the business logic.
Have a look if you can get clustering cheaply with Terracotta.
For a rewrite: Have a look at what is already present in Java EE 6. You might find it fits your needs nicely. Glassfish 3.1 will support clustering before you are done rewriting.