Thank you for the answers so far!
Also with such a critical part of your system, getting information from your user, if the service is slow or down you will run into troubles.
What specific programming languages and/or frameworks do you require a solution for? Please let me know if I missed the point completely. Thanks for your answer!
Validation is non-trivial for many fields. For example almost no-one implements email validation correctly as per the RFC because it's hard to get right, and most people just use a hacky regex that ends up accepting invalid emails and rejecting valid ones.
Or with credit card validation, many places don't validate credit card numbers (i.e doing the validation checksum, checking if the card is a mastercard that it's got the mastercard prefix) before sending them to the card processor site. If the card processing services rejects the card and the user has to re-enter the card details, chance are they won't bother and you've lost yourself a sale. If you validated for obvious mistakes on-the-fly (i.e user sees error immediately) you wouldn't lose as many of those customers.
You could also do things like supplementing the user supplied data, say the user supplies an address you could automatically geocode it and put it in a hidden field for the website.
Validation for the purpose of having clean data in your database is obviously important too, but less so. But obviously if you had a service for providing the first it wouldn't be hard to offer it as a server side services as well.
Currently frustrated that highrise does not timestamp tags, or allow tags to be sorted by a timestamp.
If you could add that feature as a plugin or via their api I would gladly pay $25 per month.
Haven't looked extensively for a solution, but it's certainly a pain point at the moment.
I'm curious, are you a developer?
If problem X and problem Y both cost $25/month to solve, they should be roughly equal pain-wise. By starting at price point of $25/month, and working your way backwards to find problems, you should expect to be tackling Github- or Basecamp-sized problems.
>I'm curious, are you a developer?
Yes, I'm a developer/consultant.
How?
Amount of Pain X Solves < Amount of Pain Y Solves
X solves a problem for a small market where the consumers are still find it worth $25 to solve the problem and have less options.
Y solves a massive problem that a lot of people have (big market). Prices have been driven to $25 by many competitors.
Different amounts of pain, different amounts of complexity, same price. Y's price has been driven down to 25 by competitive factors. X's price is higher because a lack of competitors. All this requires is that one is under-priced relative to value delivered but not to the market's competitive forces. Therefore neither is under priced given the reality of both sides of the market.
should be secure, auto detect formats, etc.
- Front end web site availability
- APIs available
- Back end processes are running
- Database up
- Disk space available
- Error logs for important issues
The database checks would include referencal integrity and sanity checks on volumes to warn of potential issues eg a failed module or abuse by a user.
Daily and weekly reports by Email, RSS, Twitter, web tool. SMS for emergencies requiring immediate action.
Option to have support from a Sys Admin/DBA automatically trigger to fix minor issues.
Looks like this: http://cl.ly/image/0Z15301Q3L1u