Ask HN: Startup Pillars
I observed for best and success product ,
we required 2 strong pillar for startup
1. Product Architecture , 2. Database Design
can any one suggest me any books, blog or any link to great and confident on this two topics
can any one suggest me any books, blog or any link to great and confident on this two topics
If you have to break it down in terms of raw basics, what approach you choose largely depends on what you want to achieve. Performance or security. wanting both requires large amount of human as well as computing resources. As a general example, consider node or apache, node gives you a performance improvement in terms of raw latency and concurrency by a factor of ~20-100 (based on a few simple tests i've done using apache bench) in most scenarios compared to apache but in terms of reliability, if your code for any reason doesn't handle exceptions, it takes down your entire server/service. With apache, that wont happen, your perfomance degrades, some users might get affected but the service as a whole would still be operational. This is just an example, most of the technology out there is about making the choice on what you're okay with comprimising with the available resources (human and computational) that you have. This is just my view on it.
followed by further reading on this https://www.ciosummits.com/media/solution_spotlight/TDWI_Che... And possibly sql query optimizations. In most cases, efficient indexes should be enough to maintain reasonable performance.
But in cases where scale gets exponentially bigger at a rate at which you cannot possibly keep adding computing resources, breaking the best followed practices is the only way to get more performance without adding hardware resources at the same rate as increased scale, this at times includes but is not limited to, getting rid of foreign keys, coupling your app logic along with your db to to breakdown larger tables periodically/automatically/ runtime creation. This though requires skills across the entire stack and has it's fair share of downfalls and is never a recommended practice unless you know what you're doing and are okay with compromising on some of ACID properties. since maintaining something like this becomes unsustainable without contingencies. Take all of this with some grain of salt as the topic is highly subjective.
Yes i will check that book and it will be helpful, for Node vs Apache, yes , as Apache is multi threaded and Node is single threaded ,if some fails single thread will die and it affect whole server