Tag Info

Hot answers tagged

4

no, there is no difference between calling an ASMX web service vs. any other kind of web service. The code on the server is not exposed because .cs files are by default not served by Asp.Net, or the code for the ASMX is compiled into an assembly in the bin folder, depending on the type of project (Web Site vs. Web Project) deployed. It may be possible to ...


2

Regarding your first question: for proper decoupling services should only store IDs of objects belonging to other services 9if they can not avoid the dependency at all). Sometimes the dependency can be extracted to a separate "hub" service whose sole role is connecting data retrieved from other services which themselves are not aware of the dependency. An ...


2

If I understood your colleague's suggestion correctly, the solution proposed was to have a web.config key that contains a type name for the implementation class. You can use this name to retrieve the type, instantiate it (or register in DI container), and use it. I.e.: public interface IAuthenticationBlaBla { ... } public class ...


1

Best pracrice is to use different classes on both sides of the service. After all if you were an external client consuming the service you would hardly have access to the service classes. However, as you point out, that is a pain. I would share the data classes. perhape compile them and stick on an internal nuget repo?


1

Wikipedia has a suitable definition for Middleware. It says: Middleware is the software that connects software components or enterprise applications. [It] is the software layer that lies between the operating system and the applications on each side of a distributed computer network. Typically, it supports complex, distributed business software ...


1

An API key is a parameter passed to the service interface, so it can be passed with any type of auth on the backend. But usually, and api key is used to determine whether a user is allowed to use a specific API. For example, if only a subset of users that have windows accounts are allowed to use the api, then maybe that might make sense, because, even if ...


1

You don't say anything about what kind of 'simple tools' you are talking about, so you just get knee-jerk answers based on what people assume it to be. If the tools are desktop apps distributed to untrusted users over the internet, then obviously it would be an incredible bad idea to allow them to execute arbitrary sql on your database server. On the other ...


1

This sounds like a perfect use-case for Apache Kafka: Each partition is an ordered, immutable sequence of messages that is continually appended to—a commit log. The messages in the partitions are each assigned a sequential id number called the offset that uniquely identifies each message within the partition. The Kafka cluster retains all published ...


1

Sure, this sort of Software as a Service stuff has existed for quite some time now. Are there any pitfalls to this setup? Yeah, non-functional internet makes it hard for web services to work without some sort of local caching layer. The latency you talk about can be a concern. It can be harder to test your application depending on how it is designed. ...


1

The pitfalls range from Nothing to Everything, with your real-world results lying somewhere in between. Standard libraries are used everywhere. For example, we have the C++ standard library that almost all C++ programs are based off of to some degree. Even this standard library changes depending on your compiler, in that the standard library that ships with ...



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