I have a conceptual design question. I'm building an application/platform that will consist of a server, possibly running Apache Tomcat w/ a MySQL database, and several client applications (such as native iPhone apps, android apps, blackberry apps). Communication between the client applications and the server will be handled via SOAP, or XML-RPC (also trying to figure this out).
All of the above I'm reasonably comfortable with, but the last part of my plan is to create web/browser based client interface to the platform. And this is where I run into my question, should I install Apache Web Server on my same physical server and build a PHP application that invokes RPC's on the Application Server (Tomcat, running on same physical machine)? Does this type of design pattern make sense? Or should I stick with one type of server software for all possible client applications, including the web/browser based application? Thanks!
I think the web server and app server ought to be separate. I'd make the database separate from the app server too, if I could.
The reason I like the web server to be separate is that it's usually in between two firewalls. The app server lives inside the second firewall in the "safe" network.
Related
We have a WinForms desktop app that connects to a remote server to pull some data. The remote server hosts a web service on a standard IIS website that queries a SQL Server database installed on the same machine. Today, if the remote server is under maintenance or not available our end-user cannot retrieve the necessary data.
Now I am requested to make this feature fault-tolerant. Here are my questions:
Should I ask for another remote server that runs the same web service and move the DB to a third remote server? So the two web services can connect to the same DB?
Should I consider moving the web service logic to the WinForms desktop app and connect directly to a remote DB paying a first-class 99.99% availability service?
Do AWS or Azure provide a ready-to-use solution that fulfills my requirements?
Is there any other option I didn't consider?
I am creating a website, using mostly html and some php pages, now I have to create a database and connect it with my website, for log in and requests, my question is what database should I go for, is Microsoft access good enough? or sql server or phpmyadmin? the website isn't large, it might get 6 requests per day, I am not a professional programmer but I know a few things about programming, please help
I am an developer in Access. Access technology is a Windows application, not intended for web applications. It is not a back end database which is what a web server needs behind it. The SQL Server - Express Edition (free) would be the product from the Microsoft family. Of course there are other suitable shareware products out there, probably the best known being MySQL.
When the requirement is for internal needs, not public facing, but the users are geographically separated; then Access (and other Windows Applications) are platformed on a Remote Desktop Server (aka Terminal Services).
The other alternative to building your own web application is using one of the database centric web services: Soho, QuickBase, Knack, etc.
I have am existing project that runs on windows, mac, ios and android. I'm looking for a way to make a windows phone version, but I can't figure out how to use SQL. My current code base is very large and I can't "switch" to using EF. How can I get access to databases in UWP?
If you want to connect a local database, for example the SQLite, there are implemented libraries could be used do this stuff:
A Developer's Guide to Windows 10: (10) SQLite Local Database
If you want to connect a server-based database, for example, the SQL Server database, unfortunately, there is not a built-in API like ADO.NET that could be used to connect the SQL Server directly. And for a workaround, you would have to utilize a middle layer for example, the WCF Serrvie:
How to access data from SQL Server database in Windows Store app, although this sample is written for store app, the used approach is the same for UWP application.
You'll not be able to connect directly to a Microsoft SQL Server database. Instead you'll need to make some type of Service layer that communicates with the database and your phone app would need to communicate with that. For more information on how to do that see the code same and the video that Microsoft has hosted here:
https://code.msdn.microsoft.com/windowsapps/How-to-access-data-from-5f2602ec
In our development team we have:
4 developers
one application uses PHP and database Microsoft SQL Server 2008r2, except one using PowerBuilder instead of PHP and one using MySql instead of Microsoft SQL Server
All applications are database-centered, some of them are for general public, some are not.
Question is: for the procedures and functions shared by all applications, what does it make most sense to use, database procedures/functions or web services?
We could not find an agreement within the team.
Whatever you answer, please explain the reasons.
Webservices and Database Proc/Functions are two entirely different things.
Webservices are the services over the web, mainly used when a client and a server interact and client interacts with the server through web or HTTP or any other protocol.
Database proc/func - are created to interact with a login to a DB server.
In your case, if all the application are in the same domain... then you dont need to access through webservices and also it is a lot of overhead.
You can create a common DB server , where you can keep these proc/func and can be consumed by all.
I have a client with a .Net 1.0 web app that uses IIS and a SQL 2000 database. It is hosted with a shared hosting service and does get not much traffic (a few visitors a day tops). The hosting has occasional downtime, of course, and the client has asked me if I can setup a redundant system to reduce downtime to negligible.
What is the simplest/cheapest improvement I could make to this setup that would satisfy what the client is asking for?
I was imagining hosting the web app and db with 2 different services and adding some logic to the app hand off requests to whichever web server & database are up, but I'm worried about the complexities of keeping the databases in sync.
Is there a better way?
i'd recommend putting and apache2 server with mod_jk in front of the two IIS endpoints.