Tag Info

New answers tagged

2

Long story short: all in one. If you consider one of these as "master" and the other as an augmented replica, that updates are replicated one way only, and you can survive large latencies in synchronisation (and I'll let you define "large") then two separate DBs will work. For anything else I'd suggest a single DB. If you have two-way updates will they be ...


2

Something to consider might be a Master Data Management (MDM) approach. It would basically consist of an operational data store for each application, each using an ETL job or replication to synchronize with a master data store. Each operational data store schema can evolve independently, with the ETL job handling any necessary translations. How often ...


2

I understand you are trying to solve two key problems here Syncing configuration files to between two locations Deploying applications from development to production. To answer your first question: There a number of sync tools that are available you can use to sync a bunch of directories to across multiple systems my favorite is rsync. ...


2

I used to work on a similar application, but the anticipated situation in my application would be very different from the way this site, facebook, twitter, or your application would work. This is just in case, this can somewhat give you some insight. I put both authentication data and business data in the same SQL database. The reasons are: When the ...


0

Treat Web services the same as any other data access: To approach client side MVC architecture, without frameworks, we treated Web services in the same manner as we did localStorage and the local IndexedDB database. All code that involves requests to remote servers or that query a database or that read/write to localStorage happen in the model layer as DAO ...


0

How do you map what the client might send you to the data the API requires? I mean if I've understood the question correctly, its about providing a webservice that wraps several other APIs, eg a pizza delivery service that passes requests on to either Tony's or John's pizza parlours, only Tony does Deep Pan and Thin Crust, and John does Traditional, ...


1

There are many ways this could be done. One way I have seen it done: A web application adds a record to a job queue. The new job ID is saved in the user's web session, to make it easier to find the jobs of the user. Another background process periodically scans the table for new jobs that have not yet been started. When it finds such a job, it then starts ...


1

Just by the question, one cannot pinpoint a single pattern because there are multiple aspects to a pattern. Depending on how your service is architected, the pattern can vary. In general, however, what you specified is the overarching Service Abstraction design principle. Also, quite often a piece of software, especially at the scope of a web-service, is ...


1

What you're describing is essentially the Adapter design pattern. You have an external component that you want to use, but it's implementation and interface is not what you want to use within your enterprise. The fact that you're exposing your wrapper as a web service is irrelevant as the pattern is still the same. You're essentially wrapping an existing ...


2

One of the simplest ways to achieve this is to use UDP broadcast. Essentially: The server listens for UDP packets on a certain port. When a client wants to connect to the server, it sends a broadcast UDP packet to the certain port. When the server sees a broadcast packet, it replies to that client with information about what the actual address/URL of the ...



Top 50 recent answers are included