Tag Info

Hot answers tagged

6

Usually, services call other services when they need to access their data. Each piece of data should belong to a particular service which will be the only entry point to accessing this data and modifying it. Some services will be simple and usually correspond closely to your domain model (e.g. a service for handling users) while others will be high-level and ...


4

Requiring a reboot of the application when the database goes down is definitely a bad design, because it increases maintainance effort which will negatively affect your uptime. A good design would try to reconnect to the database every few seconds so business can continue as soon as the database is available again. In the meantime, returning a "500 ...


4

webSocket is implemented in browsers (not in the underlying OS). It is built on top of TCP/IP which comes from the OS. You can see which versions of which browsers support webSockets here:http://caniuse.com/#feat=websockets


4

If, as you write, you directly edit files on the server over SFTP, your only option (as far as I can see) is to install git on the server, login via SSH and do all git operations locally. You'd have to create a repository on the server, add all your files and then commit regularly. In that case your working directory would be the directory where all the JS ...


3

If you allow a client to access the database directly - which they would do, even with a database abstraction layer, then: You get a coupling between their code and yours - particularly, there is a very strong coupling between your database structure and their code; Your client may do some pretty undesirable stuff on your database - whether it be updating ...


2

Yes. It is possible to patch a JAR file using jar -u. It is also possible to patch a WAR file the same way. But I would NOT recommend it. The JAR or WAR file should be the unit of deployment / management. If you start patching JAR / WAR files on production servers, it is hard to track what is actually being used where. If you are not careful, chaos and ...


1

First rule of thumb - never start over if you can avoid it. That's a Joel Spolsky rule of software development. So that's automatically a strike against re-writing your app in HTML5. Fortunately, you really only have to re-write the client. You can update the server app incrementally, but you don't need to replace it wholesale. However, moving from ...


1

I couldn't convince my boss yet that this is a bad idea, am i wrong here? I feel like a web app is not the right tool for this job. And if this is indeed a bad idea, what would the best way be for me to clearly explain him that? I am really not sure this is a bad idea. To me it sounds like a good idea because your customers will get what they want ...


1

Stick to a pure Javascript and HTML template solution to package that all up into a single minified .js file. Use sprites for fewer images. These may have their own auxiliary benefits (eg. saves bandwidth by minifying JS), but I wouldn't make any changes like this purely for reasons of making my deployment more convenient. You haven't ...


1

Yes, it is quite possible, and I have done such myself. The situation I was in was deployment of a large .war file. The web application part of it was not that big - but it also contained within it a Java Web Start application. The combined size of all of this was a few hundred megabytes. This posed a problem for deployment - when pushing all of this down ...


1

If I understand correctly what a DBAL is, then the answer is that a REST interface allows you to use any language for its clients, while a DBAL is a library that allows you to use a single language for its clients. This, in turn, can be an advantage for a company where there are many development teams and not all of them are proficient in the same language. ...


1

You are thinking that REST is for database queries and it is not. REST represents the state of something at the moment. Using REST changes or retrieves a representation but that is all. If that state becomes available by database, it doesn't matter and no one cares because HOW that representation comes to be is not part of REST and neither are database ...


1

SVN/GIT or any control version should work. Except for very specific application, web application a rarely live ( in the sense Physically loaded in memory) and i assume your application doesnt rewrite itself ( else you have the risk of rewriting the push you just made). Then if you push your file the next call on the webserver/php will load the new code ...


1

The application primarily deals with users, profiles owned by users, photos, and tags that represent one to many profiles in a photo. There would conceivably be methods to return photos uploaded by a user, return photos that contain a certain tagged profile, etc. Well, profile service should not work with user object. It may know only the ID of ...



Only top voted, non community-wiki answers of a minimum length are eligible