Judge Asks Federal Prosecutors to Investigate Uber's Self-Driving Car Program

Uber CEO Travis Kalanick

Staff / Reuters

The judge presiding over Waymo's high-profile lawsuit against Uber has asked federal prosecutors to investigate the ride-hailing company and one of its top autonomous vehicle executives for potential theft of trade secrets from the Alphabet-owned autonomous car company.

The referral of the lawsuit to the United States Attorney means that Uber is now facing two Justice Department Investigations. Waymo had also requested US District Judge William Alsup grant an injunction to halt Uber's self-driving program pending a trial. Alsup issued an order “granting in part and denying in part” that request, but the court order is still under seal. Alsup also denied a bid by Uber to force the case into arbitration.

Alsup's decision deal a significant blow to Uber, which is also under criminal investigation by the Justice Department over its use of an internal tool used to circumvent regulators. Waymo filed the lawsuit against Uber in February, alleging that Anthony Levandowski, its former employee, downloaded 14,000 files before leaving the company and joining the ride-hail giant – and then using Waymo’s trade secrets to help Uber build its own self-driving technology.

An Uber spokesperson said in a statement that “It is unfortunate that Waymo will be permitted to avoid abiding by the arbitration promise it requires its employees to make. We remain confident in our case and welcome the chance to talk about our independently developed technology in any forum.”

Uber declined comment on Alsup's referral of the case to the U.S. Attorney’s office.

In referring the case to the Justice Department, Alsup – who has thus far told Waymo it has one of the strongest cases he has seen in his career – said he takes “takes no position on whether a prosecution is or is not warranted, a decision entirely up to the United States Attorney.”

The lawsuit centers around LiDAR technology, which uses lasers to help self-driving cars see and navigate the world. Waymo’s lawyers have argued that the situation is so damaging to its own business that the court should halt Uber’s use of the technology it allegedly created using stolen trade secrets, essentially putting the brakes on the ride-hail giant’s self-driving program. Uber’s lawyers said exhaustive searches of the company’s systems have not turned up the files Waymo alleges were stolen. Whether Alsup has granted Waymo's request for an injunction – and how extensively – will become clear when the court order becomes public.

On April 27, Levandowski stepped down from his leadership position in Uber’s self-driving program and into a lesser role. Uber’s lawyers cited the move as evidence he is not working on the technology at hand pending a trial. Waymo's injunction request, however, had asked the judge to stop Levandowski from working on Uber's self-driving program entirely.

This is a developing story.

Quelle: <a href="Judge Asks Federal Prosecutors to Investigate Uber's Self-Driving Car Program“>BuzzFeed

Azure SQL Database now supports transparent geographic failover of database groups

The built-in geo-replication feature has been generally available to SQL Database customers since 2014. During this time one of the most common customer requests has been about supporting transparent failover with automatic activation. Today we are happy to announce a public preview of auto-failover groups that extends geo-replication with the following additional capabilities:

Geo-replication of a group of databases within a logical server
Ability to choose manual or automatic failover for a group of databases
The connection endpoint to the primary databases in the group that doesn’t change after failover
The connection end-point to the secondary databases in the group that doesn’t change after failover (for read-only workloads)

Geo-replication of a group of databases

A typical cloud application includes multiple databases. You can now use Azure SQL Database API to protect the application by geo-replicating all its databases in one simple step. During an outage, all these databases will failover to the secondary server as a group. The group can include individual databases, elastic pools or a combination of the two. If you are already using geo-replication for your production databases you can create a failover group and add them to it to take advantage of the above benefits at no extra cost.

Connection endpoints

You no longer need to worry about changing SQL connection string after failover. Each auto-failover group includes two connection endpoints. The read-write endpoint is a DNS name that will always point to the primary database and will automatically switch during failover. The read-only endpoint is a DNS name that points to the secondary server and allows using the secondary databases to load balance the read-only workloads. 
Quelle: Azure

Elastic Load Balancing: Account Limits API

We are pleased to announce that Elastic Load Balancing now provides an API that can be used to access service limits for Application Load Balancers and Classic Load Balancers. Prior to the availability of this API, customers needed to contact AWS Support or use Trusted Advisor in order to check their existing service limits for load balancers.
Quelle: aws.amazon.com