Is it bad to use many web services on a business web application


0

I'm the sole developer on a web application project that a friend and I started up. I'm handling development and my friend is handling the business side. It's a guerrilla operation and with what our application is trying to achieve I could never develop it on my own in a reasonable time. So I'm planning on using many services to run the application. AppFog for hosting and deployment, MongoHQ for the database, Searchify for document indexing, Filepicker.io for file uploads, and AWS for misc utility needs. Besides the obvious worry about one of these companies going under, are there any other reasons why I should absolutely not be doing this?
I figure if our application actually takes off and we make any kind of revenue, at that point, I could then put resources into building solutions to take the place of different web services I'm currently using.

Web Services Web Dev

asked Jul 27 '12 at 08:42
Blank
Derek
1 point
  • Do you have an alternative? Write a DB engine yourself? Or search engine for you documents? – Salmon 7 years ago
  • This is an application architecture question, better to ask on StackOverflow probably (with the question reworded and specified). – Ekoostik Martin 7 years ago

2 Answers


2

  • If you're paying all the licenses and fees as you should be (and not breaking terms of service)...
  • And you're not guaranteeing some sort of an up-time that's quite impossible to keep...
  • And you have a backup plan should one of your main service providers goes under or changes terms that make it impossible for you to use...
  • And you're aware of integration and update effort if you're relying on a large number of external services

then you should be OK.

I don't think using many services is bad in itself - it's neither productive nor reasonable to build everything by yourself.

answered Jul 27 '12 at 10:20
Blank
Jjj
21 points

0

You definitely want to leverage what is out there, but protect your core competencies.

The earlier point about building in flexibility in case you need to swap providers is a very good one. In Object Oriented design, that is called an abstraction layer. Your tech team should design for flexibility and anticipate swapping things out down the road.

Also consider how slow the site will load if the back end jumps off to half a dozen APIs spread out all over the cloud.

answered Aug 27 '12 at 07:22
Blank
Nw Architect
136 points

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Web Services Web Dev