I am learning back-end development by developing a C# Web Service that interacts with a database. I am not sure, however, where the database is supposed to be kept. Is it supposed to be in the same location as where the web service will be hosted?
[1]Yes,Usually Hosting provider will provide you database with any of your chosen plan like Shared Hosting/VPS Hosting/Dedicated Server.So you should keep your database in hosted environment.
[2]Take backup and keep a copy of it with your local system by FTP transfer.
Related
Currently I'm working on a project where we use React, PWA, PouchDB and CouchDB to build an offline first application with a large amount of data from the remote database, stored in the client web browser.
In other words a local database of around 2GB is stored in the client through IndexDB storage.
There is a significant problem on the replication of the remote database when starting the application and building the local database. PouchDB takes too long to do this process, there is a thread speaking about this topic.
pouchdb replicate from couchdb : very slow
Apparently there is no way to speed up PouchDB in the level that we need for the project. Therefore we have considered other options for a local database in the web browser with synchronization to a remote database. Some of the options we have considered are AWS Amplify Datastore, Firebase Cloud Firestore and Minimongo.
The company I work for is strongly linked with Azure services, but I have not found any like service in Azure that stores large amounts of data in the client web browser and synchronizes with the remote database.
Does anyone know of an Azure service that can help with this project?
If not, is there any other option or architecture even if not Azure, that would be recommended. We already have a functional web application with React, PWA, CouchDB and PouchDB, this is NoSQL, so NoSQL options would be preferred, but I'm open to consider SQL Database options even though a bigger modification would need to be done in the program.
Thank you in advance !!
I am using the OCN-client locally. I run it in memory, without a database. How does it work? Will it be a problem for me when developing my backoffice service?
The in-memory database is good for development (the OCN client will forget connected parties on restart), but when moving to testing and production phases you would want to switch to a persistent database.
Assuming I want to develop a Win 8/10 universal app eg calendar, the user has a two devices tablet/phone.
How can my calendar share a local SQL database?
I don't want to maintain or administer an azure service or any other remote DB service ie AWS, VPS running SQL Express etc.. which is overkill for such a basic scenario.
I have considered SQLite and dumping the DB file in the users MS OneDrive folder but as we know this could result in sync/lock issues.
So using a purely self contained & free model, how can my two devices share this basic SQL data?
If the database is small you can save it in the RoamingFolder and let Windows take care of copying it to the other system.
See Quickstart: Roaming app data
Other than that storing the data in a cloud service such as an Azure Mobile App Service is the easiest and cleanest solution. Azure Mobile Services support offline sync to SQLite if you need to support both online and offline scenarios.
Saving app data on the user's OneDrive or dropbox and then explicitly downloading it to use is possible but more difficult and a bit dirtier since the data will be visible to the user and could be accidentally deleted, moved, etc. For a personal app it's not bad but I wouldn't do this in production.
If you're copying the database between systems (either via roaming or via a data storage site) you'll need to devise a way to handle conflicts. This is simpler if everything is kept in a single cloud database.
I am a new user to openstack trove. As far as I found (from the process of creating datastore and database in trove) trove works like this: For each datastore instance there is a nova-compute image that this instance will be launch on that (and also a cinder storage assigned to this instance) Therefore there is not a centralized database which could be manage by openstack administrator. As far as I know there are two types of cloud database: 1)virtual machine image database and 2)dbaas. For dbaas it should not be like having a virtual machine instance per each database and database provisioning should be manageable by system administrator (not client). Therefore could somebody explain for me how trove works and how could we consider it dbaas and not virtual machine image database?
Regards.
Trove is an openstack service that provides an API for creating a relational or non-relational database to a user. This database can be used within a deployed application. So in your terms it is a database as a service solution.
Trove provisions an instance from an image for a single tenant. This is not meant to be a centralized database for openstack.
To get more details about Trove
https://wiki.openstack.org/wiki/Trove
I am working on a phonegap project to build a cross platform mobile app, and came to know from a website that the app's database can be deployed/built with "database.com".
The procedure is well explained but I have one question -
how to sync the database available on database.com with a database on a local server?
i.e. for e.g., if a client has his database (of his desktop application) on his local server and he requires a mobile app of the same now, what is the procedure to be followed in "database.com" to sync his server's database with the database on "database.com"?
PS: I need to use "database.com" for my database because I want to maintain it on cloud, and I do not have capability to maintain a local server.
You might need a service for data syncing if it is to be more than once. I work on a project that does exactly this.
www.overcast-suite.com
Otherwise, model your tables to Salesforce Custom Objects, export the data on the local server to CVS and use the Data Loader to import.