At the end of the day they are offering a lot more than just 10k. They are offering training AND placement assistance. They are also assuming the costs of the people who fail to complete the program of get a job.

They also seriously need to give CloudWatch a UI/UX overhaul.

1. https://opencensus.io/introduction/#partners-contributors

Would also be nice to see some stats for traffic within the same AZ as well. I generally see ping times between 0.1 and 0.2 ms within the same AZ on AWS, would be nice to know what that looks like on Azure and GCP.

I think there is still value in Blockchain networks like Stellar[1] that are not fully decentralized, but are federated and diverse. If this is a first step towards them issuing a stable coin on a network like that then I welcome it.

1. https://www.stellar.org

MS could certainly also do good business selling Docker's friendly Enterprise orchestration tools (including their new Kubernetes based tool) which check all the Enterprise requirements for security, policy, identity management etc.

> A second important theme for decentralized systems is a common lack of appreciation for just how complex these systems are and how finely balanced they need to be to operate correctly.

I originally joined Bittorrent in 2007 to work on a decentralized CDN which aimed to do something like “tie together all the unused storage and bandwidth on people’s PCs into a content delivery network which had zero operating costs (for us)”.

In time it proved there were a number of things wrong with this ambition (most of which I won’t touch on here), although perhaps the most important one which we discovered the hard way was the cost of complexity.

1. https://medium.com/@simonhmorris/intent-complexity-and-the-g...

Key snippets:

> And this is the main conclusion — decentralization may be great for disruption, but if the experience of Bittorrent is anything to go by it is not at all clear that it has a role in whatever comes next. Blockchain architectures are great for unleashing unstoppable rule-breaking mobs, but we shouldn’t mistake the rule-breakers for the winners.

> Perhaps one of the most far-sighted winners here was Daniel Ek — CEO and Founder of Spotify — who preceded his Spotify success with the sale of the uTorrent client to BitTorrent Inc. Although early versions of Spotify used a Bittorrent-like P2P protocol to try to save money on bandwidth, they quickly realized that the main point of Bittorrent had little to do with saving money, and decentralization of their architecture was actually counter-productive to their aim. Perhaps it was apparent to them way back then that leading a revolution is exciting, but it’s far better to build the thing to save incumbents from the unleashed mob.

1. https://medium.com/@simonhmorris/decentralized-disruption-wh...

Comments URL: https://news.ycombinator.com/item?id=18899186

Points: 3

# Comments: 3

Reliability is the trickiest of the three because it requires the customer to architect their solution with multi-AZ support in mind, but AWS always provides the foundation for that architecture.

Could they, and should they provide more features and a better developer experience around building fault tolerant solutions? Absolutely! But I certainly don't think they have a bad reputation for reliability.

As far as being "viable to trust a business on" the numbers don't lie, AWS is number one because customers are running their businesses on AWS. The fact that DocumentDB launched with supporting quotes from Capital One, Dow Jones and WaPo shows that customers were clamoring to use it even before GA.

Remember a lot of these customers are coming to AWS because they tried doing themselves and stuggled. When it comes to data, customers trust AWS more than they trust themselves, and rightly so.

The downside is that a lot of their products lack polish which sucks. On the flip side even when they are launched with minimal features, they do tend to be reliable, durable and secure, which is important when it comes to data related services.

Then again, the relationship between AWS and Oracle is even more contentious and Aurora MySQL is one of AWS's most popular products so I don't think they are terribly worried about building on competitor's technologies.

1. http://www.wiredtiger.com/

I wonder if it is that they just have a so much r4 inventory left that they are forcing us to use it or if they haven't fully integrated/validated the latest instance types with their custom storage backend.

I am however really hoping Amazon provides a MySQL 8.0 compatible version of Aurora with full support for its new hybrid SQL and Document Store interfaces[2] courtesy of the X DevAPI[3] and lightweight "serverless" friendly connections courtesy of the new X Protocol.

That way your don't have to choose just one approach, and you can have your data in one place with high reliability and durability.

My ultimate pipe dream would be that they also provided a redis compatible key/value interface that allows you to fetch simple values directly from the underlying innodb storage engine without going thru the SQL layer, similar to how the memcached plugin currently works[4]

1. https://github.com/wiredtiger/wiredtiger

2. https://mysqlserverteam.com/mysql-8-0-announcing-ga-of-the-m...

3. https://dev.mysql.com/doc/x-devapi-userguide/en/devapi-users...

4. https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached.htm...

> At re:Invent 2018 we announced Firecracker, an open source virtualization technology that is purpose-built for creating and managing secure, multi-tenant containers and functions-based services. Firecracker enables you to deploy workloads in lightweight virtual machines called microVMs. These microVMs can initiate code faster, with less overhead. Innovations such as these allow us to improve the efficiency of Fargate and help us pass on cost savings to customers.

Also seeing interesting Firecracker developments around OSv (7ms boot times)[2] and Kata Containers[3]

1. https://firecracker-microvm.github.io/

2. https://twitter.com/osvdev/status/1081461689139281920

3. https://twitter.com/egernst/status/1076308458335494144

> At re:Invent 2018 we announced Firecracker, an open source virtualization technology that is purpose-built for creating and managing secure, multi-tenant containers and functions-based services. Firecracker enables you to deploy workloads in lightweight virtual machines called microVMs. These microVMs can initiate code faster, with less overhead. Innovations such as these allow us to improve the efficiency of Fargate and help us pass on cost savings to customers.

Also seeing interesting Firecracker developments around OSv (7ms boot times)[2] and Kata Containers[3]

1. https://firecracker-microvm.github.io/

2. https://twitter.com/osvdev/status/1081461689139281920

3. https://twitter.com/egernst/status/1076308458335494144

> At re:Invent 2018 we announced Firecracker, an open source virtualization technology that is purpose-built for creating and managing secure, multi-tenant containers and functions-based services. Firecracker enables you to deploy workloads in lightweight virtual machines called microVMs. These microVMs can initiate code faster, with less overhead. Innovations such as these allow us to improve the efficiency of Fargate and help us pass on cost savings to customers.

Also seeing interesting Firecracker developments around OSv (7ms boot times)[2] and Kata Containers[3]

1. https://firecracker-microvm.github.io/

2. https://twitter.com/osvdev/status/1081461689139281920

3. https://twitter.com/egernst/status/1076308458335494144