Honestly I didnt even know how to give this topic a Headline so please don't hold it against me.
So here is my scenario, I have been a ASP.NET dev for a while and have lived in that comfort zone of SQL Server and C# or basically the MS universe denying the requirement that i would ever need to consider the LAMP solution.
So along came the day where i Began researching a idea and found that the cost of the MS universe is just plain rediculous hence i am now a PHP/MySQL Noob
Firstly i have never worked with data that would go beyond certain limits so it was always pretty straight forward development however my current project could potentially scale one day and hence meaning we would perhaps use MySQL master/slave solutions, MySQL Database Pooling, And lastly if it ever gets there Sharding.
Now since i am at the starting phase of development thinking ahead i am trying to forsee what we might encounter and reduce impacts and development changes etc.
So i have been debating the Store Procedure Route as should we ever scale and maybe shard do Stored Procs need to be customize to read from those different sources or will they automatically adjust with some miracle MySQL capabilities.
I have considered the ORM method for CRUD operations and Also the Procs Route for Our Reporting Aspects but i find it hard to know what side effects i will face with the stored procedure routes later on.
The Project will include Mobile. Will Require Continuous Searching as there will be a Search feature based on the information and there will also be Reports both Predefined and also Custom for the Clients to select what to compare on the Fly so what method would one suggest for this.?
Everyone i spoke to with a little knowledge and i also agree SQL procs Prevent injection and add a little speed benefit and reduce network traffic but is that really a gain as it could count against you at a later point in the game.
any assistance in this regard will be helpful thanks.