As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Our current system is based on a Spring/Hibernate/Java/MySQL stack. We have a relationship with a company for which we will end up doing a portion of the IT work. They are currently building a system using an outside vendor which is based on PHP/MySQL. I would like to make an argument that they should reconsider and switch to a Java-centric platform. My main argument is that we can utilize our current (Java-based) skillset for system maintenance and enhancements, instead of having a system which requires knowledge of both PHP and Java. However, they have asked if there is any technical reason why this couldn't happen.
It would be great if I could bring some technical arguments to table which show the two platforms are incompatible. However, I've googled the differences, and as far as I can tell, there wouldn't be any particular technical issues. For example, we could use web services for the systems to communicate.
So, the question is, is there anything one could say about PHP which makes it either incompatible with or just not as "good" as Java? E.g security, scalability and other enterprise considerations? I know it's a vague question, but it would be very helpful to get some input.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I was asked this questions in one interview.
Suppose there is a requirement of highly concurrent application e.g. Email application like Gmail where in
say there 100K users accessing the application at the same time.
You are allowed to ask only 3 questions to client which 3 questions will you ask?
Client in this case is company who want the application to get developed. e.g.Google [Disclaimer: Name is
just to give idea. I know what you must be thinking :) ]
I was really confused there can be n number of questions starting with technology, hardware configuration etc. Can some one tell me which can be best suited questions in above case.
SLAs (expected uptime, response times, usage patterns, etc.)
How much can be spent on maintenance (servers/cloud, support)
Expected growth
Budget?
Desired delivery date?
Do you have a pen to sign or will you need one?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Subjective Logic is fundamental as part of my next project, and I was just wondering if there are any implementations already out there. I've read some things (not a lot) about the operators but I'm still unsure as to how it is implemented.
Preferably I would like a C/Java/Go/Python implementation
I dont see any example codes for subjective logic after a google search. This concept is more into AI and logic based languages like Prolog will have to be employed. Also if you have a rule evaluation engine (like CLIPS rule-engine as mentioned here), then good to go.
There are couple of algorithms proposed which leverage subjective logic and can be coded in java or C right away.
The demo page contains a Java applet which can be used to visualise networks of trust using subjective logic. While no source can be obtained for the applet up front, the applet JAR file can be decompiled using a program such as JD (java decompiler) and from there reverse engineered.
The code somewhat provides a library and is the only example of subjective logic in code I've seen.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I know there are some differences between both of them, but suppossing that you already have a fully-operating Java environment for developing, testing and production, will you ever consider using Ruby MRI instead of JRuby? On top of that, I would also argue that you can inline Java, use Java datatypes and, most importantly, it almost always outperform Ruby. What do you think? Is there any reason why one should consider Ruby seriously when compared to JRuby?
It's all about choice. If JRuby makes more sense to you use it. Using MRI means you're using Ruby the way Matz has intended it.
This should also answer the question for Rubinius, Maglev and all other implementations. Each serves a different purpose and tries to cover all aspects of MRI. To achieve that they (all) use RubySpec to test the implementation against MRI.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Anybody knows a good book that can help me understand test driven programming and how it is done in jee6? Ive never really used that approach(or at least correctly). I am very curious abut this topic i would like to give it a try in my java web projects.
So if any good literature recommendation, please let me know.
You don't need a book for that, to my opinon. You need to know, how to create and run unit tests (for different programming languages and frameworks).
The idea of test driven development (TDD) is fairly simple:
read the requirements (no requirements -> no TDD)
write a test, that tests the requirements. The test will fail initially.
write code until the test passes (and don't write any extra stuff!)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
What are the main advantages (and disadvantages) of using of an Application Server, comparing to a standalone application? I'm interested in Java approach mainly.
With an application server, the developer should spend time writing business logic (which delivers added-value) rather than boilerplate infrastructure code (e.g. managing transactions, configuration, security, etc.). So to me, the main argument is that using an application server should boost the productivity.
Unfortunately, the learning curve until you can unleash this productivity boost is rather long. In the worse case, misusage of application server features can even result in a productivity loss.
Also a general problem with any approach that raise the abstraction level (same with MDA, etc.), is that when something goes wrong it's harder to understand how to fix or circumvent the problem. On the other hand, if you do everything yourself at a lower abstraction level, you know how to fix problem easily but you re-invent the wheel again and again.
This is a high-level view of the concept of application server. For details about technical features of Java EE application servers, refer to the Java EE documentation or the link in the 1st comment to your question.