Today, we’re announcing Firmina, an open subsea cable being built by Google that will run from the East Coast of the United States to Las Toninas, Argentina, with additional landings in Praia Grande, Brazil, and Punta del Este, Uruguay. Firmina will be the longest cable in the world capable of running entirely from a single power source at one end of the cable if its other power source(s) become temporarily unavailable—a resilience boost at a time when reliable connectivity is more important than ever. 

As people and businesses have come to depend on digital services for many aspects of their lives, Firmina will improve access to Google services for users in South America. With 12 fiber pairs, the cable will carry traffic quickly and securely between North and South America, giving users fast, low-latency access to Google products such as Search, Gmail and YouTube, as well as Google Cloud services.

Single-end power source capability is important for reliability, a key priority for Google’s network. With submarine cables, data travels as pulses of light inside the cable’s optical fibers. That light signal is amplified every 100 km with a high-voltage electrical current supplied at landing stations in each country. While shorter cable systems can enjoy the higher availability of power feeding from a single end, longer cables with large fiber-pair counts make this harder to do. Firmina breaks this barrier—connecting North to South America, the cable will be the longest ever to feature single-end power feeding capability. Achieving this record-breaking, highly-resilient design is accomplished by supplying the cable with a voltage 20% higher than with previous systems.

Celebrating the world’s visionaries

We sought to honor a luminary who worked to advance human understanding and social justice. The cable is named after Maria Firmina dos Reis (1825 – 1917), a Brazilian abolitionist and author whose 1859 novel, Úrsula, depicted life for Afro-Brazilians under slavery. A mixed-race woman and intellectual, Firmina is considered Brazil’s first novelist. With this cable, we’re thrilled to draw attention to her pioneering work and spirit. You can learn more about Firmina in this Google Doodle.

Including Firmina, we now have investments in 16 subsea cables, such as Dunant, Equiano and Grace Hopper, and consortium cables like Echo, JGA, INDIGO, and Havfrue. We’re continuing our work of building out a robust global network and infrastructure, which includes Google data centers and Google Cloud regions around the world. 

Learn more about our infrastructure.

Assembling thousands of parts into one motorbike or scooter every 17 seconds is a complex task requiring accuracy and precision. For Hero MotoCorp — an India-headquartered manufacturer of two-wheeler vehicles — workforce collaboration, security, and mobility complement these processes and provide the cornerstone of the organization’s global operations.

Based in New Delhi, Hero MotoCorp is one of the world’s largest makers of two-wheeler vehicles, with a production capacity of 9 million units from five manufacturing plants in India and one each in Colombia and Bangladesh. The business has more than 90 million customers and operates in 37 countries across Asia, Africa, and South and Central America. In its home market, HeroMotoCorp sells one in every two two-wheelers.

Innovation and agility

Innovation and agility are deeply embedded in Hero MotoCorp’s culture and operations. Its Center of Innovation and Technology at Jaipur in Rajasthan, northern India, undertakes extensive product design and development, testing, and validation.

Hero MotoCorp has also established a technology center at Stephanskirchen, near Munich in Germany, to develop new vehicle concepts and technologies.

For several years, Hero MotoCorp relied on a traditional email solution to enable its employees to communicate and complete tasks. However, this solution could not provide the functionality, performance, ease of use, and security the business needed to maintain its market leadership.

“Our Chief Information Officer, Mr. Vijay Sethi, was the first to migrate to and embrace the features of G Suite and set an example to our workforce.”

Sujoy Brahmachari, Sr. GM and CISO, Hero MotoCorp

“Security, in particular, is extremely important — we don’t want our product design and development details falling into the wrong hands,” says Sujoy Brahmachari, Sr. GM and CISO, Hero MotoCorp. “We needed a solution that would allow us to control and monitor the distribution of sensitive information within and outside our organization.”

In early 2015, Hero MotoCorp’s technology team began evaluating email and workplace collaboration applications that could help the business realize its longer-term ambitions.

Collaboration key to success

“We were focused on a product that could drive greater collaboration among our workforce,” says Brahmachari. “In addition, we wanted to use the product on our desktops, laptops, mobile devices, and other devices. Finally, we needed to ensure email, other applications, and data were secure and available as and when we needed them.”

Hero MotoCorp’s evaluation found G Suite met all these requirements while being intuitive and easy to use. Furthermore, the cloud-based suite of intelligent applications provided a lower total cost of ownership than the business’s existing email solution and potential alternatives.

A 45-day migration

The business completed its review and completed the migration in just 45 days in 2015. “We worked closely with Google and our partners to complete the process in an innovative way that prioritized speed,” says Brahmachari. “For example, we migrated only three months’ worth of emails from our incumbent solution to G Suite, rather than the entire data repository.”

“Our teams are very happy and collaborative – employees can use Gmail through G Suite without being concerned about storage limits and can connect with colleagues, partners, customers, and other stakeholders through the chat, video, and audio call capabilities of Hangouts Meet.”

Sujoy Brahmachari, Sr. GM and CISO, Hero MotoCorp

Hero MotoCorp started the migration with a function-wise approach, creating batches and moving them overnight to G Suite. It created an internal video for employees to learn how to work using G Suite. It also created intranet posts to provide easy reference to all employees and established a service desk to respond to questions.

“Our Chief Information Officer, Mr. Vijay Sethi, was the first to migrate to and embrace the features of G Suite and set an example to our workforce,” says Brahmachari.

Deployed to 6,000 users

Hero MotoCorp has deployed G Suite to about 6,000 users in its core business and many users in affiliate companies. The company’s user-focused approach to the deployment, and the intuitive, easy-to-use nature of the product, has prompted the business’s workforce to embrace the full potential of G Suite.

“Our teams are very happy and collaborative — employees can use Gmail through G Suite without being concerned about storage limits and can connect with colleagues, partners, customers, and other stakeholders through the chat, video, and audio call capabilities of Hangouts Meet,” says Brahmachari.

Employees can also create, store, and access Docs, Sheets, Slides, and other file types on Drive — helping to ensure new product development, delivery schedules, budgeting, and other activities needed to keep a leading multinational manufacturer ahead of its competitors can be completed quickly and collaboratively.

Deployed to mobile devices

“With G Suite, information is available in the cloud to any employee at any time. The collaboration this enables plays a vital role in sustaining our leadership position.”

Sujoy Brahmachari, Sr. GM and CISO, Hero MotoCorp

Hero MotoCorp has also been able to give employees access to G Suite on a range of mobile devices — with administrators using mobile management to secure access applications and data on iOS and Android devices. The business is using the feature to require devices to have a screen lock or password; remote-wipe information from lost or stolen devices; and monitor from a central console the devices that access corporate data.

Further, Hero MotoCorp can use G Suite features to set and enforce policies and control system configuration and administration, while taking advantage of independently verified security, privacy, and compliance controls to meet business requirements.

With G Suite deployed and delivering value, Hero MotoCorp is now implementing or evaluating a range of Google technologies. For example, the business is using Google Maps Platform to power navigation for owners of new Hero MotoCorp two-wheelers and use Cloud Vision AI to enable immediate recognition of spare parts. “We are also evaluating Google Cloud data search and management technologies for potential application within the organization,” says Brahmachari.

The business is now well-positioned to accelerate into new markets and product development. “With G Suite, information is available in the cloud to any employee at any time,” says Brahmachari. “The collaboration this enables plays a vital role in sustaining our leadership position.”

Since its initial release in 1995, MySQL has not only been the de-facto database for many data storage needs, but has gathered much attention over the years as one of the most well-recognized databases around when it comes to Relational Database Management Systems and transactional data processing.

Any application in retail, e-commerce, or banking has likely had its fair share of business depending on a relational database for its transactional needs. Many of these applications are built on MySQL due to its flexibility, open source nature, and strong community support.

Whether in the context of a migration from a relational database (like MySQL or PostgreSQL) , migration from a NoSQL database (like Cassandra), or a green grass workload, many companies turn to Cloud Spanner seeking a high availability SLA (99.99% for regional instances and 99.999% for multi region instances),  unlimited scale,  and low operational overhead – no patching required, no maintenance or other planned downtimes, just to name a few benefits.

The tooling and open source ecosystem around Spanner has evolved and grown ever since the service was introduced. HarbourBridge is a part of this ecosystem, and it’s meant to help customers port their existing MySQL or PostgreSQL schema to a Cloud Spanner schema. 

Application Migration Tips

Despite helpful tools like HarbourBridge, database migrations are never trivial. Here are a few things to pay attention to when migrating from MySQL to Spanner, and how to update your application logic to address them.

Note – The following snippets use the PHP client for Cloud Spanner. A couple of the snippets reference a partial Magento port that our friends over at Searce have been working on. Once you understand the operations, you should be able to implement the same in any of the other languages that Cloud Spanner supports.

Cloud spanner enforces strict data types  

In a MySQL query, the value of an attribute can be referenced as either a string or an integer. Example:

• select * from catalog_eav_attribute where attribute_id = 46;
• select * from catalog_eav_attribute where attribute_id = “46”;

Both are valid and equivalent. 

In Cloud Spanner, the query will return an error if you try to reference an integer type by using a string representation.

Here is an example of a working query from Cloud Spanner:

• select * from catalog_eav_attribute where attribute_id = 46; — this will work
• Select * from catalog_eav_attribute where attribute_id = “46” — will fail, since we are supplying a string with “46” 

You may use a function like the following to assist you with such transformations.

  /**
    * Formats the SQL for Cloud Spanner
    * Example
    * Input SQL : <select statement> WHERE 
    *    (`product_id` = '340') ORDER BY position  ASC
    * Output SQL : <select statement> WHERE 
    *    (`product_id` = 340) ORDER BY position  ASC
    * In the above example integer 
    *`340` is sanitized by removing single quotes.
    * Sanitization is required since Cloud Spanner
    * has strict typing
    * @param string $sql
    * @return string $sql
    */
   public function sanitizeSql(string $sql)
   {
       if (preg_match_all("/('[^']*')/", $sql, $m)) {
           $matches = array_shift($m);
           for($i = 0; $i < count($matches); $i++) {
               $curr =  $matches[$i];
               $curr = filter_var($curr, 
                   FILTER_SANITIZE_NUMBER_INT);
               if (is_numeric($curr)) {
                   $sql = str_replace($matches[$i], 
                       $curr, $sql);
               }
           }
       }
       return $sql;
   }

Using sequences in primary keys is not a Spanner best practice

Cloud Spanner does not implement a sequence generator,  and it is not a Spanner best practice to use sequential IDs because doing so can cause hotspotting.

An alternative mechanism of generating a unique primary key is to use a UUID or any other similar mechanisms that result in non-sequential values. For more information, please refer to this article.

In order to convert all existing primary keys to a UUID pattern, you can change the schema using the snippet here

You may use this code snippet to modify the application code to generate the UUID for the auto increment. There are other ways to do this as well, such as using PHP built-in uniqid function.

  /**
    * Generate UUID.
    * @return string
    */
   public function getAutoIncrement()
   {
       if (function_exists('com_create_guid') === true) {
           return trim(com_create_guid(), '{}');
       }
       return sprintf('%04X%04X-%04X-%04X-%04X-%04X%04X%04X',
           mt_rand(0, 65535), mt_rand(0, 65535),
           mt_rand(0, 65535), mt_rand(16384, 20479), 
           mt_rand(32768, 49151),  mt_rand(0, 65535),
           mt_rand(0, 65535), mt_rand(0, 65535));   
   }

Implicit casting and the need for explicit casting of field data types 

Both MySQL and Cloud Spanner follow the SQL standard, hence much of the query syntax is the same. One notable difference is that the Cloud Spanner field types are implicitly cast to an appropriate data type out of the ones mentioned here. When implicit casting of the field type fails, Spanner returns a read error, so it would be safer to perform the casting to the appropriate type when issuing the SELECT statement.

Modify application code to cast to respective data type before execution of query.

  $con = $this->getSpannerConnection();
 /**
 * Cloud Spanner follows strict type so cast the columns appropriately
*/
$select = $con->addCast($select, "`t_d`.`value`", 'string');
$select = $con->addCast($select, "`t_s`.`value`", 'string');
$select = $con->addCast($select, "IF(t_s.value_id IS NULL, 
    t_d.value, t_s.value)", 'string');
$values = $con->fetchAll($select);

Modify the application code to cast the column to its respective type 

  /**
    * Cast the column with type
    * @param string $sql
    * @param string $col
    * @param string $type
    * @return string
    */
   public function addCast(string $sql,
       string $col, string $type)
   {
      $cast = "cast(".$col." as ".$type.")";
      return str_replace($col, $cast, $sql);
   }

Using interleaved tables to improve read performance

Cloud Spanner’s table interleaving is a great choice for many parent-child relationships where the child table’s primary key includes the parent table’s primary key columns. Interleaving ensures that child rows are collocated with their parent rows, which can significantly improve query performance.

Refer to the statements here for a few samples of creating interleaved tables. To learn more about table interleaving, visit the documentation.

Conclusion

Database migrations are complicated.  Hopefully, using HarbourBridge and the  list of tips in this article can make that task easier.  For additional tips, please take a look at this migration guide and read more about HarbourBridge.

As a leading French agricultural cooperative, Groupe Dauphinoise places collaboration at the heart of its philosophy. Working with farmers in the Rhone-Alpes region, Groupe Dauphinoise takes on a diverse range of activities from agricultural production to research and development to running retail outlets.

As its operations expanded and strained its existing infrastructure, Groupe Dauphinoise saw the opportunity to upgrade its technology solutions and adopted G Suite, Chrome devices and ultimately Google Cloud Platform (GCP).

“We transitioned to G Suite to improve our staff’s collaboration. We quickly realized that as the company grew, we needed a new infrastructure. Based on our satisfaction with G Suite, we chose GCP. With Google, ‘any device, anytime, anywhere’ is not just a dream,” says Sylvain Claudel, Head of IT at Groupe Dauphinoise.

“We transitioned to G Suite to improve our staff’s collaboration. We quickly realized that as the company grew, we needed a new infrastructure. Based on our satisfaction with G Suite, we chose GCP. With Google, ‘any device, anytime, anywhere’ is not just a dream.”

—Sylvain Claudel, Head of IT, Groupe Dauphinoise

Flexible workforce, stable infrastructure

Many of Groupe Dauphinoise’s 1,500 employees spend their days out of the office. Five years ago, with the help of Google partner GoWizYou, the company transitioned to G Suite to improve the flexibility and collaboration of its staff.

As Groupe Dauphinoise began to expand and collect more data, the company reached the limits of its on-premise infrastructure. Adding new storage was not a simple matter. Acquiring, configuring and synchronising new servers costs Groupe Dauphinoise time as well as money. In addition, with all its servers stored in a single room, security was a concern. Groupe Dauphinoise needed a new infrastructure.

Google Cloud Platform was the only solution in mind after Groupe Dauphinoise’s experience with G Suite and Chromebooks. Disruption was kept to a minimum thanks to Google’s licensing agreements with Microsoft products, allowing the company to migrate without affecting its operations.

After migrating its infrastructure to Compute Engine, Groupe Dauphinoise can let Google look after the security and maintenance. Cloud IAM makes it easy for Groupe Dauphinoise to hand out permissions to sensitive resources across a number of sites with maximum security and minimum fuss. The company placed its archives in Cloud Storage, while Cloud SQL allows it to continue to make use of its MySQL databases without disrupting the day to day business. Meanwhile, BigQuery provides Groupe Dauphinoise with the raw power to analyse large datasets quickly.

“Our company is growing and we have more and more data to collect and analyze like sales data, weather patterns or production numbers. With GCP, we have more than a single on-premise data store, so our disaster recovery plan is much more flexible. Compute Engine allows us to add more storage quickly and easily, without having to spend days synchronizing data and installing new servers. We have improved security and maintained the stability of our infrastructure while keeping costs down,” says Sylvain.

Safeguarding the present, looking to the future

With Google Cloud Platform, Groupe Dauphinoise has expanded and secured its infrastructure without sinking costs into on-premise servers or DevOps staff. Its investment in Chrome devices and adoption of G Suite mean that its mobile workforce can fully reap the benefits of a cloud-based infrastructure while dramatically cutting the cost of hardware. Meanwhile, working with a 200 million line table of sales data in Google BigQuery, the cooperative found that queries ran ten times faster than with its previous database provider. Groupe Dauphinoise is experimenting with Google BigQuery to expand its BI capabilities. Products like Google BigQuery help Groupe Dauphinoise grow its business, safe in the knowledge that its infrastructure is stable and secure.

“The amount of data we collect is growing very quickly. We need to break our rules and evolve from the mindset that we had with on-premise infrastructure and our old databases. We can now look at collecting more customer fidelity data, or big data for our farmers. With our data and infrastructure in Google’s care, we can concentrate on growing our customer base instead of our IT department!” says Sylvain.

We are pleased to announce the availability of Google Cloud Monitoring uptime checks in the Google Cloud mobile app. 

The uptime check capability offered by Cloud Monitoring is a simple yet powerful observability tool to monitor an application’s availability and performance on URLs provided by customers. The primary purpose of an uptime check is to track resource availability on an on-going basis. It’s essentially a pulse check for a system and is often the first to detect impending issues. Using uptime checks can proactively detect availability and latency issues with an application and reduce the time and severity your users are impacted by an outage. Uptime check can validate if the response code from your application is as expected, and also the latency of your service from different regions. Uptime checks can further inform your SLAs and SLOs, and track your service’s health over time. SREs at Google use uptime checks as an important part of their daily routine.

Given the critical role served by uptime checks, we heard your feedback on having the ability to track these checks in the Google Cloud mobile app. With this launch SRE’s, operators or administrators can do exactly that, in addition to easily accessing their cloud resources (App Engine, Compute, Databases, Storage), managing permissions using IAM, viewing logs, incidents, errors, and billing.

To access uptime checks, simply tap the “Operations” tab in the Google Cloud mobile app on your iOS or Android device.

After navigating to “Uptime Checks”, you will see a list of all the services you have previously added using the Create public uptime check documentation.

The list is sorted by status, so all failing checks are at the top. You can easily filter by status using the “Filters” option in the top-right corner of the screen.

Tapping any of the uptime checks will take you to the “details”-screen.

Here you’ll see your application’s uptime, latency, status per region (if you’re monitoring your application from more than one cloud region) and graphs to give you a sneak preview. The “passed check”-graph is showing how many checks passed in the last hour up to 6 weeks. You can easily change the interval using the scale above the graphs.

Scroll down the page to see more data. At the bottom of the screen, we’ve included some configuration details for this uptime check, so you can check the above data against this specific setting.

We hope you find this new uptime check feature useful in your daily work. To create new uptime checks, start here: Create public uptime check.

We’re working hard to make the Google Cloud app your companion for monitoring and managing your Google Cloud resources on the go.

For pricing information on uptime checks, please see the Cloud Monitoring pricing summary.

This new feature is available for you to use today. If you have any feedback, we would love to hear from you — just click the “Send feedback” button in the app. And if you don’t have the app – go ahead and download the app today from Google Play or the Apple App Store.