1 in 5 requests should be to the database. You should then also be extensively using Caching methods in all Tiers, so that the Database isn't being accessed all the time. You'd then have Api and Web server software replicated over various machines with a Load Balancer directing traffic. so therefore: Database is on one machine, Api is on another machine and Presentation is on a third (either a mobile or web server). though these really only come in as a problem when you have a big database of million and millions of records.Īlso one should choose wisely the database that your using, for example, for a freight application you should really still be using an RDBMS database like Sql Server or MySql and not a NoSql Database - which was designed for Big Data that doesn't change (e.g Comments and Messages).Ĭloud also doesn't remove the need for Application Tiers (a Tier is a machine or VM) and you should be using at least a 3 Tier solution. First it's a misconception that is happening when it comes to Cloud solutions that they improve performance over apps, the Cloud Server was designed to remove the problem of needing to have Server maintenance teams who do little more than check that a machine is switched on.Ĭloud doesn't override the need for good database design (Normalising Data) and efficient Indexing of tables.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |