Jordan Novet in a GigaOm post about the initial lack of security features in Hadoop:
Hadoop, the much-hyped software for processing large amounts of data on commodity hardware, has its roots in indexing tons of webpages for a search engine, not handling credit card numbers. And it wasn’t developed from the start with security in mind.
- I really don’t know how many popular and widely used storage solutions have their roots in handling credit card numbers.
- I really don’t know how many popular and widely used storage solutions have been developed from the start with security in mind
- I don’t know of any NoSQL databases that failed to be adopted because it was/is lacking security features1.
Bottom line, security features are critical for some users. Plus security features should never be taken light. And while it’s true that every lacking feature is limiting adoption, projects need to weight very well where the focus goes. Basically, if you don’t have a long list of customers handling credit card numbers, don’t focus your new database on this feature.
In the early days most of the NoSQL databases completely lacked any security features. But if they didn’t get the adoption they dreamed about that wasn’t caused by this. ↩
Original title and link: Built for handling credit card numbers ( ©myNoSQL)