yeraydarias

Probably, but some initial solutions are worse than natural design, it is only a starting point. And of course it could be helpful for some kind of special situations.

There is another problem. The uncertain future.

When you start using a NoSQL solution it can be nice and fit the problem quite well. Then the solution gets bigger, new features appear and new data is stored, but the storage is NoSQL. With the solution getting bigger some business intelligence could be required by marketing or other people in the company. But we all know that NoSQL solutions aren't so good with aggregated queries, but in the rush it is hard to slow down to create a second solution for this kind of queries.

So, yes, you are right when you say "People not understanding what NoSQL is good for and when to use it over relational". But the main problem is that you don't know the complete problem in advance usually.

Sorry I didn't answered previously about the number of local machines. Actually it depends much more on the network configuration than the number of machines itself in our case.

We used two machines to simulate up to 600 requests per second, that was much more than our average use, actually much much more. And we measured it without HAProxy or Varnish or similar systems between our servers and the clients.

Yeah sure, depends on your architecture and the kind of application ... in our case we had one machine scraping data and writing it in the database. One backend machine to organize the scrapers data and to do some organization tasks. And finally the front was two machines.

At first those 4 machines were hitting the database so much that it was the bottleneck, what we did to solve that was to reduce the number of accesses done by the front machines using a memory cache. It can increase the latency when loading the cache but works fine 95% of the time.

Another option for us could be a larger database machine, but we were using Amazon RDS ... believe me you want to keep that machine as small as possible or expend a lot of money :-)

That is a good and necessary recognition, not only because she deserves it. I hope it will not change with the current changes in the White House.

This will help girls to have a heroine, to feel good about wanting to be a software developer or an engineer. And I hope it will open people eyes about software wasn't only for men.

I'm from Europe so I don't know in detail how USA works. But I guess it is quite similar to Europe, the price of the phone will rise so much that it won't be a good product. In the best of the scenarios the price will rise 20$ or 30$ ... well maybe, but launching a product is not always the best of the scenarios.

Apple already told in the past, that the main reason to keep the manufacture in China are the last minute changes. USA or Europe cannot deal with that kind of changes and the labor laws that we have doesn't help ... just my IMHO. Labor laws and labor conditions in China or India are cruel, but works for capitalist markets.

We made some stress tests in the past and it is quite useful.

We did it with Gatling (a very known tool in the Java world) in some of our local machines requesting our machines in Amazon EC2.

As it was commented previously, the test depends on various points, to tell a few: * Do you want to test a complete web or just a few services? * The speed of your system depends on the number of instances or there are other points to look like the database connection? * Do you want to test vertical scale or you want to know about the horizontal scaling too?

We did the tests mainly to know the "breaking point" of our database that was our "weakest link".

Anyway, stress tests are quite useful and give you an idea about how much your system can scale and helps to detect where to improve code before expending too much money in servers.

hehehe, good luck ... you never know what will happen until the traffic came :-)

Both books are good, and I don't believe Clean Code is praising the glory of agile dev, it talks about technical good practices ... practices that can be applied to any objected oriented language in general, doing agile or waterfall or whatever ... IMHO.

Yes, it is a very complex book, but without any doubt THE BOOK if we are talking about compilers. A must if your want to know how a compiler works.