Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I know this as been asked but couldn't find an answer that I understand...
Some people told me about the main thing are sagas, but it doesn't look such a big advantage to make me spend my bucks on NServiceBus when I already have MSMQ....
That's a little bit like asking "why do I need ASP.NET MVC when I already have HTTP?"... a little tongue-in-cheek, but still with a lot of truth in it.
NServiceBus gives you message serialization, a sensible threading model, routing, and several ready-to-use messaging patterns out of the box.
MSMQ gives you... message queues! And a fairly complicated API with many low level options that give you no real pit of succes...
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 4 years ago.
Improve this question
I want to go with Xamarin.Forms project. Now, I am bit confuse for consuming Rest API for this project. Performance matters.
There are many available but can any body please suggest me which should be best for Xamarin.Forms(.Net Standard)?
Microsoft Http Libraries or third party libraries like Refit, RESTSharp, PortableRest, etc.
Please suggest
All of these options are viable. I think the performance differences between these libraries will be marginal. So, it mostly comes down to what you feel comfortable with.
I like to use Refit because it will take a lot of redundant code out of your hands and you just have to focus on the contract. All the code for the actual calls is generated at compile-time (and thus won't impact your performance at runtime).
Also have a look at how well the library is maintained and if it's active. If you choose one that is already inactive for a while, chances are that you will start relying on older software versions which might not be what you want.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Why is REST an architecture style whereas SOAP is considered as a protocol? Please explain.
Architecture is about high level design. REST is an example of that because it is only a set of design guidelines like that your API should be stateless. It doesn't tell you exactly what language to use or what your code should look like.
Other examples of architectural questions are
How should my modules communicate?
How should I structure my data?
What guiding principles can I apply?
Non examples are:
What is the name of the function that allocates memory?
Do I use i++ or ++i?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I've seen plenty of posts on the pros and cons of the EF but finding quite hard to find anything on the relationship between EF and project management methodologies such as Waterfall SDLC and Agile?
Would anyone have any links or information on the above? Thanks.
Frameworks and methodologies are typically orthogonal.
The only (indirect) relationship is that Agile methods would have you build your application to be decoupled from the persistence mechanism altogether. In fact, you would delay even using a database until you have a user story that requires that you have one. This would force you to keep the two decoupled, leaving your options open.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to create a REST based chat application in Java using Eclipse, but I have no idea how to start. How do I take care of resources, verbs, and HEATOS.
Check out this link, or this link, or this link. I would personally recommend Jersey. restelt is very powerful, but might be quite complicated. RESTeasy has more features than jersey, but it can also be a pain to configure outside JBoss, and their community is not as 'active'. I would recommend Jersey, their startup tutorial is very easy to follow.
You can also look at this book, and this book. Sorry, I can't provide any hard answers as I have no knowledge, your level of expertise on the subject. Hope this helps.
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 6 years ago.
Improve this question
Developing software solutions which already exist and are available for re-use (either commercial or open-source). AKA "re-inventing the wheel".
Same as above, but your solution being broken. AKA "re-inventing the square wheel".
Developing solutions for problems which do not exist.
Again, I'm interested in a more formal approach, e.g. TRIZ
Doing some research beforehand (1) and investing in solid software architecture (2,3) usually helps :)
When you're planning to develop something you always need to calculate the benefits of doing some and the things like the ROI.
You could read more about this in Agile Estimating and Planning by Mike Cohn
Local Market Research
Internet Research
Google Metrics (Seeing what the Google Count is)