Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I searched on Google, but didn't get straight answers that what are the advantages of Service Oriented Architecture?
Can someone please highlight some of the benefits of SOA?
The two most important (at least in a practical sense) are:
Small, manageable (i.e. maintainable) components.
Services can be distributed across different machines. This makes
the system highly scalable.
In other words: SOA is a good fit into the modern software development landscape with distributed teams and ever-changing requirements, be it functional or non-functional.
It gives great deal of re usability to your code and enormous power to the business as well.
Lets say you start creating an application for banking, now you need to create a mobile app for the same, and if that's not it you have to expose methods from your service to Master /Visa for transaction.
Now in the above scenario if application has been designed with SOA in mind, then lot of code is reused with added advantage of centralized deployment.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Django uses a threaded architecture unlike Play framework which uses Evented architecture.
I wanted to compare Django with Play framework. Which one performs better if we deploy the services written in Django and Play on the hardware with same configuration, also given that business logic for the service has been written effeciently in both the frameworks? Which framework has the potential to scale to 1000+ concurrent requests?
Threads and events are not a dichotomy, Play gives you threads and an event loop.
This question is too broad, it really depends on what you're trying to implement - in many many use cases the web framework is not the bottleneck, it's the database. But if you insist on getting on a comparison that completely ignores whatever your specific use case is, then here's a comparison:
http://www.techempower.com/benchmarks/#section=data-r9&hw=peak&test=json&f=2hwco-0-0-0
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am currently doing Computer Science degree and I have fair amount of experience in C#, Java, and C++ in desktop application development. And I want to start learning how to build applications that run in the web browser such as Google Docs and Blackboard Learn. What is the best technology to start with ? I know this is a broad question whose answer is usually "it depends on what you are trying to make" but I want to know what is good multipurpose language/technology just to start with so I can get some experience and develop some foundation for transitioning my desktop skills to the web ? Many thanks for your responses !
I would suggest you to list all your requirements. After you are done with the requirements you can select what suits you the best. Current web applications use a cocktail of several technologies. The choice of technology should be purely based on your requirements, ease of use and budget constraints.
Of course, you have a plethora of several open source technologies to help you out. Biggies such as Facebook, Google too use open source. Since you are a student go for open source technologies.
This is a good link if you want to learn web from scratch : http://www.w3schools.com/
Thanks
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am currently at about the 50% point in a web app's development, getting to this point by rapidly coding followed by refactoring. After reviewing with the client again at this point, the scope of the project required for completion is clear and unlikely to change.
Is it advised at this point to start implementing tests? If so, do I create tests for the functionality already completed or prioritize TDD for the remaining parts of the application?
As mentioned in the comment by #zerkms it is usually advisable to use TDD for new functionality, and when you change existing behaviour.
To guard the functionality you currently have, use some integration tests and smoke tests for some typical, and crucial scenarios. Don't aim to achieve high coverage with these tests, as it will be to much of a burden to maintain them in the future. If you will be persistent at writing unit tests for discovered bugs and new stuff in time you will get high coverage.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I consider to use Mantis or Redmine to manage projects. (Issue Tracking)
I know both are really good.
For now, I won't connect it with SVN or Git.
(It may happen later)
The main purpose is issue tracking on business with co-workers.
Please recommend one of them, or you can recommend the other one.
Thanks.
I can recommend redmine. I've been using it for more than 2 years, with 25-50 simultaneous users and more than 50 projects.
I went through a lot of updates without ever having any problems.
The database is properly normalized, so if you ever need to retrieve any data, you will be able to do so.
Numerous plugins exists which may cover special needs if there are any.
Edit: In the meantime, I had to change over to Jira, but I'd go back to redmine anytime if I could.
Never used Redmine, but we've been using Mantis for about 7-8 years for many projects for our distributed team. One of the benefits is its simplicity. We've even wrote a couple of our own extensions, e.g. widely used in our process Kanban board (one of the Agile approaches).
Sometimes I think it looks slightly outdated among other modern tools but it really works for us and we can extend it with our own PHP code.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
How does Staff web service framework compare to others for c++?
I cannot answer your question in all details, but I'm searching for C++ SOA / web service frameworks for a year now.
My favorites (all OpenSource and platform independent - not ordered) are currently:
GSOAP - http://www.cs.fsu.edu/~engelen/soap.html
pros:
proven, reliable, very fast
big documentation, many support
still maintained - releases every 3-6 months
contras:
WSDL/client generators are not free
programming and embedding into existing apps isn't so easy
seems to be more C than C++
Apache AXIS/C++ - http://ws.apache.org/axis/cpp/index.html
pros:
proven, already in use in big projects
(nearly) good documentation
up to date, maintenance is ensured by Apache Foundation
better/nicer C++ API
contras:
heavy weight SDK / too many functionality for me
not easy to implement it / many work to embed it into own app
maybe not as fast and bigger footprint as GSOAP
Staff - http://code.google.com/p/staff/
pros:
very small footprint
easy and fast to integrate
contras:
future maintenance is not clear / it's (only) a Google summer of code project
very early stage
support party only in cyrillic
If I have to decide for a framework right now, I would take Apache AXIS -
it's proven and reliable and thus ready for productive use.
Further it's future maintenance is guaranteed by the Apache Foundation
and I'm free to uase, modify and integrate AXIS as I want - even for my
commercial applications.
I hope that helped a little bit.