what is the best approach to come out of managing too many webservices in an application?

Question

2.00/5 (1 vote)

See more:

We are working on an application that has about 70 web services. Now managing each of these is become a mesh and for each new feature people are creating new services again and again since nobody dare to modify the existing services.
Now we are looking for best solutions to come out of the services mesh.
please redirect me if any one has faced and fixed this issue.

Posted 4-Aug-14 21:41pm

muralinarisetty

Add a Solution

Comments

Sergey Alexandrovich Kryukov 5-Aug-14 3:47am

Sorry, this is too vague and not enough informative. How can we know what are the aspects of your management, what problems do you have with that, even why does it "has" about 70 Web services (and what this "has" means? using? controlling?...)
—SA

Dimitri Nostarik 5-Aug-14 3:57am

+1 - Did not have to type the same thing - Will include an (attempted) answer.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dimitri Nostarik · Accepted Answer · 2014-08-04T21:58:00

You have an application with a multitude of web services? You do not want to manage all of these yourself?

Here's an idea, build an application that manages these services. You can make it GUI friendly for your co-workers, so they can easily find the specific web service, and modify it. Doing this also makes it possible (with SQL, or something) to create a website for it, so the users can do it themselves.

Best Regards,
- Dimitri

Worried Brown Eyes · Accepted Answer · 2014-08-04T22:26:00

Hi.

All these web services have interfaces, don't they? Who is designing these interfaces? If it is each developer as they see fit, then this is the root of your problem.

A good first step would be to make it someone's (or some team's) job to manage these interfaces, that way, they can be responsible for grouping related functionality into fewer services & providing documentation so that developers know whether what they are implementing already exists, and how to access it.

You would then be in a much better position to implement Dimitri's solution, if required.

Hope this is useful.

Regards, Stewart

what is the best approach to come out of managing too many webservices in an application?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0