datasage

Australia is has low bandwidth to the rest of the world largely due its geography and capacity/path of the undersea cables connecting the country.

Geographically its relatively close to Singapore (compared to other data centers anyway), all of the cables from the eastern side of the country either go up to Japan via Guam or go to the US via Hawaii. Its not uncommon to see a route from Sydney to Singapore go through the US, and/or Japan before reaching Singapore.

Actually, the results are reverse from what you said (y-axis is the origin). It likely has to do with traffic congestion coming out of each datacenter. Virginia has by far the heaviest use out of all the datacenters.

Some of the costs from vendors may also increase as a result.

All it manages to show is that as a designer he is not very original and maybe influenced a bit too much about what he is inspired by. But this in itself is not a copyright violation.

By growing and getting into new markets you can stay ahead of the curve. But once you hit saturation, its going to catch up with you. On top of that there is fatigue for this model all together.

Not a law, its an industry standard. Its enforced by the card companies (Visa, etc) but generally only if you are processing enough transactions.

As I understood it, these batteries power auxiliary systems.

The biggest barrier to competition is infrastructure. Both the cost of, and getting the permitting necessary to build it.

If the infrastructure is managed by a public/private entity, then any number of companies could provide service over it.

The phone is GSM based, Verizon and Sprint use CDMA. If the market for the phone was just the US, making it GSM only may not be a great choice. However, outside of the US, the rest of the world is almost exclusively GSM.

I suspected it has more to do with duplicate orders getting canceled. I was able to snag one as well about 30 minutes ago.

With Valve, nVidia and others doing work to improve Linux gaming, it may soon become a serious gaming platform. Which is fine by me as gaming is the only reason I have a windows computer.

Micro uses a different CPU provisioning model than all the other instance types. While most instances have a guaranteed CPU allotment, micro instances do not. They can burst up to two ECU, but will eventually be limited to something around 0.1 ECU if you exceed the burst period.

That's not to say they don't have their uses, but they will not handle much traffic unless its heavily cached (but then you only have so much memory).

If you have a blog that is static and uses external js components for things like comments (disqus), you could use it in conjunction with cloudfront to handle quite a bit more traffic. Most traffic would be routed via cloudfront. Admin panel would be handled on a subdomain.

Having used both doctrine and used a format of array mappings, I prefer the doctrine way of using annotations.

However I do also acknowledge that putting important information into comments can be somewhat dangerous. Doctrine does support storing metadata in yaml and xml files too, but in that case you need to ensure that changes to your model class get reflected in the mapping file.

- The proper way of doing an audit (and search later) is to make an independent collection with a reference to the other(s) document in a different collection. Then you can index by user, date, or any other field and leave the main collection alone. The described embedded access collection doesn't look very scalable.

I think this point is very important even in the RDBMS side. There are cases, even with relational datastores that would preform better if the dataset was built to the query.

The difficulty comes into play when you are trying to keep the denormalized data up to date based on changes within the base dataset.

Moving DNS servers can usually be done with no downtime. All you need to do is copy your current dns records to a new provider and then change the name servers. Keep your old DNS configuration up at least for a few days.

Gradually clients will switch over to the new DNS servers, but as long as both servers resolve to the same IP you should be fine.

The power issue only struck 1 of the 5 zones in US East (Virgina)

I can't speak to why Heroku was impacted as much as it was. It could be that they have single points of failure, or run at a utilization level that makes losing a single zone difficult.

This certainly can happen. You can't rely on being able to launch enough replacement instances if a zone fails.

You can at least mitigate it by keeping utilization of your instances below what would be needed to handle load of one zone failing. I suspect to save money, many people are pushing utilization as high as possible.

Netflix does, but considering the time, running out of capacity after loosing a zone might have been more of an issue.

They do have a red icon if an event impacts an entire region. If a customer is correctly utilizing multiple availability zones, a failure in one zone should only impact the customer until they can fail over (Should be within minutes if they are automated).

It seems to line up pretty well if you consider it round trip commute time.

This has been happening for awhile. Although smart phones certainly do make it easier for more people to do it.

I think retailers can combat that in a few ways, but its effectiveness will vary by industry.

1. Have amazing customer service. Sales people who know and understand the products and not push a bunch of useless extras. People still like to buy from people, not robots (includes brain dead sales people)

2. Carry mostly only store brand merchandise (See furniture stores like Crate & Barrel or West Elm). If you want a particular product, you have to buy it from that company, either in store or online.

3. Carry products from manufacturers with tight price controls (See Apple). Retailers used to try to get around manufacturer price controls to have a lower price, but now that might actually work for them.

There are a lot of people still switching to MongoDB for various reasons, but its no longer the cool kid on the block and thus not a lot of people are going to brag about switching to it.

I think a lot of people switched to it because it was cool, and maybe assumed that it could solve any application data storage problem and are now finding out that it may not have been a great choice for them.

I don't think its appropriate to take away from this that MongoDB and/or other document stores are bad. Instead, I think its important to understand how they work and decide how well it applies to your use case. It's not going to work well for all applications.

Pretty much any sane architecture has machines dedicated to handling the data store (MySQL, Mongo or whatever). If you are scaling up from a single machine, this is the first split you make.

What it did not account for is a shift in the wealth gap and a stagnation of wages, relative to inflation, for a majority of people.

The wage base will need to be adjusted to reflect these changes. The last time it was changed was 20 years ago under Reagan.

Even current gaming engines can be used to produce some very amazing visuals, but games still have to be able to run on hardware that is 5 years old.

Its not very cost effective to create content at a quality that only a small number of users are going to be able to see.

While I agree there are schools that are terrible, student success is not solely the responsibly of the school. A child that is in a stable home environment that values education and exploration can probably do just as much as a good school can.

Now we tend to self segregate and choose to live in places with people like us. As professionals choose to live in cities instead of suburbs, schools around them will likely be better funded.

In places like ND, you can have a few people move in and see large gains in relative population.

Now, there are parts of ND that are growing, which is largely attributed to oil sands exploration. Which is attracting blue collar workers from some of the declining cities.

Maybe its just me, but there seems to be a bit of confusion between frameworks and language. Or many its that some languages are now rarely seen out of the frameworks that made them prominent.

Because PHP was built for a web environment and has features that make it quite useful out of the box, for that environment.

With Ruby or Phython you need to do extra work or jump into a framework to get to that "starting point". However, if you are going to start comparing Ruby/Python with a framework to PHP, then you need to look at PHP through one of the prominent frameworks out today (Symphony, ZF, Etc). Otherwise you are comparing apples to oranges.

RDBMS's, put a large focus on data integrity and access within the datastore layer itself (To differing degrees); NoSQL systems more or less offload that responsibility into the application layer. There is still a responsibility of running it within a trusted network.

This is a decision that may not be appropriate for everyone, but that does not make it wrong. Many people who used mySQL to power web applications did use just one credential to access the database. In that scenario the authentication overhead is pretty much just a waste of time.

I agree with this. We have been able to absorb displaced workers because the economy had been growing at a rate higher than natural growth (population/inflation). But the us economy has matured, it is no longer growing dramatically as it once was. While some technological advancements can create new markets and growth for the economy; Many technologies are designed to address inefficiencies in the market or business processes which will ultimately result in a net decrease in employment.

Also, technology is also a poor business decision if it costs more than existing methods taking into account increases in productivity.