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 3 years ago.
Improve this question
I am a newbie Java EE 6 Developer (EJB 3.1 ; JPA 2.0 ; JSF 2.0; etc..).
I want to start learning SOA using Java. I found 2 ways:
SOAP: which is complicated and boring to learn; the only strong point: is the UDDI/WSDL listing
REST: easy to learn & to deploy; many strong points : performance, security, speed...
My question: What the market needs now? SOAP or REST? If I choose REST, it will be the right choice ??
This will depend a lot on your business area. For fast moving technology areas such as back end for mobile phone apps, ticket systems, anything Google or areas where you have most of the control yourself - REST is probably the best choice, but if you work with business areas that changes technology slower, SOAP is still dominant and will be for a very long time. Examples are banking, medicine etc. It is often the same areas that get a lot of value out of the strict WSDL design.
it is no "right" choice, it depends on what you are working with, and what kind of systems you plan to integrate with. That being said, REST is probably the architecture for the future.
to get more information, read this:
Representational state transfer (REST) and Simple Object Access Protocol (SOAP)
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 3 years ago.
Improve this question
We're evaluating ITextSharp (now known as IText) for producing pdf documents. This will be used in our websites which will be published across a load-balanced solution amongst several servers.
According to Itext, this will require a production license per server (we're not open-source) in our load balanced configuration, as well as uat and developer licenses. This is obviously a considerable investment.
Could anyone recommend any alternatives to reduce the costs?
Also, is there a pattern we could adopt to minimise the migration effort of the existing website prototype if we were to use another product?
You could change your architecture a bit and have a dedicated PDF generation server. You'd then need to boil your requests down to something that could be sent between the servers. Depending on your goals, that could be something relatively simple, such as a user ID and a report name, or complex (text layout, that image there).
As far as distancing yourself from the commercial iText, there are two options.
1) Use the older MPL iTextSharp. It won't have all the latest features and bugfixes, but it's hard to beat the price.
2) The "wrapper" design pattern. Build a relatively generic interface, and have your current implementation of that interface sit atop iText. If you later need to swap it out, you're rebuilding the glue code, not your whole app.
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
What does a true REST architecture looks like ? I mean from a developers perspective what can be done in order to have a true REST Architecture.
So I've read some articles and according to this one link,
there are 4 levels. Well WebApi provides you with the minimum in order to have REST (URI + HTTP verbs). What about The 4th HATEOAS? How would one implement this level, what are some good practices, why is it good to have it?
Are there any other things that a good REST Architecture should have?
What does a true REST architecture looks like ?
A true REST architecture looks like the world wide web.
The REST interface is designed to be efficient for large-grain hypermedia data transfer, optimizing for the common case of the Web -- Fielding, 2000.
Generic browser communicating with generic servers, using standardized messages and media types.
There's no particular reason that I should be able to use the same client to answer questions on stack overflow that I use to watch funny cat videos, and no particular reason that I should be able to use that same client to search for videos, or shop for books, play chess, read the news, etc.
Are there any other things that a good REST Architecture should have?
Hypermedia. The "HTML" part of the Richardson Maturity Model, and the key element of "hypedmedia as the engine of application state".
The ability to communicate to the client "there is another resource over there, and it understands these standard messages" is a really big deal.
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 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 5 months ago.
Improve this question
I'm currently developing a micro service that basically provides calculation services to other micro services. It does not store data or have any resources like a sales order. It only calls other micro services and then calculates metrics and prices to return a result.
I'm kind of struggling trying to make a rest API with resources names that are nouns when all I do is calculate stuff and return results (more like an action).
So can we have a micro services that behaves more like an HTTP API than a Restful service (is it a bad practice, an anti pattern , an architecture smell, ....)
Regards
You can use whatever you want and in your particular case I am pretty sure you won't see any drawbacks. From my point of view only difference with rest is mostly semantic -some people may also argue about cacheability but I don't think so-
Apart from rest/rpc creating microservices without any actual domain could cause a maintenance issue in the long run as you totally depend on some other microservices data whenever a change required in their side you may also need change this microservice. That is why I don't recommend those kind of calculation services unless you have a valid scalability requirement.
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 5 years ago.
Improve this question
I am studying the current architecture of uber rider app and I got to know the current rider app was evolved from MVC to a specific architecture called riblet, which is designed on top of viper by Uber themselves. As I understood riblets is independently testable pieces that each have a single purpose. I'm aware that the new architecture is capable of handling performance and scalability. I am interested in knowing the cons of riblet architecture.
Okey. I found some cons of the riblet architecture. I will post them here to discuss with anyone who is interested. The main cons are as follows,
Since there is a higher number of independent riblets communicating through their interfaces, there is a probability of failure of a particular interface compared to a system with fewer components.
Yes testing a single riblet is easy yet it makes integrations and handling the requests among riblets more complicated.
Changing the technology stack in the long run is difficult