Your database decision could come back to haunt you The New Stack