Wunderkind Leverages Google Cloud to Address the Growing Needs of its Customer Base
5339
Of your peers have already read this article.
1:30 Minutes
The most insightful time you'll spend today!
Editor’s note: We’re hearing here how martech provider Wunderkind easily met the scaling demands of their growing customer base on multiple use cases with Cloud Bigtable and other Google Cloud data solutions.
Wunderkind is a performance marketing channel and we mostly have two kinds of customers: online retailers, and publishers like Gizmodo Media Group, Reader’s Digest, The New York Post and more. We help retailers boost their e-commerce revenue through real-time messaging solutions designed for email, SMS, onsite, and advertising. Brands want to provide a one-to-one experience to more of their customers, and we use our extensive history with best practices in email marketing and technology to help brands reach more customers through targeted messaging and personalized shopping experiences. With publishers, it’s a different value proposition, we use the same platform to provide a non disruptive and personalized ad experience for their website. For example, if you are on their site and then you left, we might show an ad tailored to you when you come back later – depending on the campaign.
After running into limitations with our legacy database system, we turned to Cloud Bigtable and Google Cloud, which helped us be more flexible and easily scale for high traffic demand – which can be a stable 40,000 requests per second, and meet the needs of our growing number of data use cases.
Three different databases power our core product
In our core offering, companies send us user events from their websites. We store these events and later decide (using our secret sauce) if and how to reach out to those users on behalf of our customers. Because many of our customers are retailers, Black Friday and Cyber Monday are big traffic days for us as. On such days, we can get 31 billion events, sometimes as many as 200K events per second. We show 1.6 billion impressions that have seen close to 1 billion pageviews. And at the end of all this, we securely send about 100 million emails. We noticed the same thing for election time; traffic reached the same high volume. We need scalable solutions to support this level of traffic as well as the elasticity to let us pay only for what we use, and that’s where Google Cloud comes in.
So how does this work? Our externally facing APIs, which are running on Google Kubernetes Engine, receive those user events—up to hundreds of thousand per second. All the components in our architecture need to be able to handle this demand. So from our APIs, those events go to Pub/Sub, Dataflow and from there they are written to Bigtable and BigQuery, Google Cloud’s serverless, and highly scalable data warehouse. This business user activity data underpins almost all our products. Events can be things like product views or additions to shopping carts. When we store this data in Bigtable, we use a combination of email address and the customer ID as the Bigtable key and we record the event details in that record.
What do we do with this information next? It’s important to mention that we also mark the last time we received an event about a user in Memorystore for Redis, Google Cloud’s fully managed Redis service. This is important because we have another service that is periodically checking Memorystore for users that have not been active for a campaign-specific period of time (it can be 30 minutes, for example), then deciding whether to reach out to them.
How we decide when we reach out is an intelligent part of our product offering, based on the channel, message, product, etc. When we do reach out, we use Memorystore for Redis as a rate limiter or token bucket. In order not to overwhelm the email or texting providers we send API requests to, we throttle those requests using Memorystore. (We prefer to preemptively throttle the outgoing API requests as opposed to handling errors later.)
When we do reach out, often we will need details for a specific product—let’s say if the website belongs to a retailer. We usually get that information from the retailer through various channels and we store product information in Cloud SQL for MySQL. We pull that information when we need to send an email with product information, and we use Memorystore for Redis to cache that information, since many of the products are repeatedly called. Our Cloud SQL instance has 16 vCPUs, 60GBs of memory and 0.5TB of disk space and when we perform those product information updates, we have about a thousand write transactions per second. We are also in the process of migrating some tables from a self managed MySQL instance, and we keep those tables synchronized with Cloud SQL using Datastream.
Our user history database was originally stored in AWS DynamoDB, but we were running into problems with how they structured the data, and we’d often get hot shards but with no way to determine how or why. That led to our decision to migrate to Bigtable. We set up the migration first by writing the data to two locations from Pub/Sub, performed some backfill of data until that was up and running, and then started working on the reading. We performed this over a few short months, then switched everything to Bigtable.
So, as mentioned, we are using Bigtable for multiple databases. The instance that stores our user events has about 30 TB with about 50 nodes.
Profile management
A second use case for Bigtable is for user profile management, where we track, for example, user attributes based on subscription activity, whether they’ve opted in or out of various lists, and where we apply list-specific rules that determine which targeted emails we send out to users.
Our very own URL shortener
Our third use case for Bigtable is our URL shortener. When our customers build out campaigns and choose a URL, we append tracking information to the query string of the URLs and they become long. Many times, we are sending them via SMS texts, so the URLs need to be short. We originally used an external solution, but made the determination that they couldn’t support our future demands. Our calls tend to be very bursty in nature, and we needed to plan for a future state of supporting higher throughput. We use a separate table in Bigtable for this shortened URL. We generate the short slug that is 62 bit-encoded and use it as the rowkey. We use the long slug as a Protobuf-encoded data structure in one of the row cells and we also have a cell for counting how many times it was used. We use Bigtable’s atomic increment to increase that counter to track how many times the short slug was used.
When the user receives a text message on their phone, they click the short URL, which goes through to us, and we expand it to the long slug (from Bigtable) and redirect them to the appropriate site location. Obviously, for the URL shortener use case, we need to make the conversion very quickly. Bigtable’s low latency helps us meet that demand and we can scale it up to meet higher throughput demands.
Meeting the future with Google Cloud
Our business has grown considerably, and as we keep signing up new clients, we need to scale up accordingly, and Bigtable has met our scaling demands easily. With Bigtable and other Google Cloud products powering our data architecture, we’ve met the demand of incredibly high traffic days in the last year, including Black Friday and Cyber Monday. Traffic for these events went much higher than expected, and Bigtable was there, helping us easily scale on demand.
We are working on leveraging a more cloud native approach and using Google Cloud managed services like GKE, Dataflow, pub/sub, Cloud SQL , Memorystore, BigQuery and more. Google has those 1st party products and we don’t see the value in rolling out or self managing such solutions ourselves..
Thanks to Google Cloud, we now have reliable and flexible data solutions that will help us meet the needs of our growing customer base, and delight their users with fast, responsive, personalized shopping messaging and experiences.
Learn more about Wunderkind and Cloud Bigtable. Or check out our recent blog exploring the differences between Bigtable and BigQuery.
3917
Of your peers have already downloaded this article
5:30 Minutes
The most insightful time you'll spend today!
The 2019 Accelerate State of DevOps Report confirms analyst reports that DevOps is crossing the chasm with the proportion of elite performers almost tripling compared to last year.
The report finds that delivering software quickly, reliably, and safely is at the heart of technology transformation and organizational performance. The report also finds that there’s a right way to handle the change approval process, and it leads to improvements in speed and stability and reductions in burnout.
Download this report and get:
- Insights on how to achieve elite performance in software development and delivery so you can deliver more value to your customers and stakeholders.
- Role of cloud computing in driving technology and organizational performance, with guidance on how to improve your use of the cloud.
- Smart ways to improve productivity and how the highest performers scale DevOps to maximize success.
Are You Providing Sufficient Digital Leadership?
4976
Of your peers have already read this article.
5:00 Minutes
The most insightful time you'll spend today!
It has been seven years since Marc Andreesen’s famous article “Why Software is Eating the World” was published in the Wall Street Journal, and given the slow pace of change in many companies, some executives still may not be taking the threat of being “eaten” seriously enough.
Software, and platform business models based on software, have the potential to deliver powerful economic forces into virtually any company or industry. Every company has valuable assets—such as data, expertise or access to certain services or user bases—and most of these assets can be delivered via software. Once an asset is expressed as software in a modern way—that is, as an application programming interface (API)—it can be combined with other software to create new applications and digital experiences.
Benefits of this approach, just to name a few, include near-zero marginal cost to scale up APIs for new users or use cases; global reach for both partners using APIs and end users consuming the digital experiences those APIs power; and network effects triggered as more partners use a given company’s digital assets and spread its services into new markets and use cases.
Disruption by software-powered business models
In the last two decades we’ve seen individual companies and entire industries upended by these kinds of software-powered business models. Examples abound: Amazon and the retail industry, Netflix and movie rentals, Uber and ride hailing, Airbnb and hotels, etc. We’ve reached the point that these companies’ names have become verbs synonymous with being “eaten” by software (e.g., “Amazoned” or “Netflixed”).
The most famous examples of digital disruption involve digital natives, of course, but legacy businesses are leveraging software to evolve too. Brazilian retailer Magazine Luiza—a company I’ve worked with through my employer, Google Cloud’s Apigee team—has enjoyed enormous revenue growth and seen its stock soar, for example, as it has built out its digital platform capabilities and transitioned from a primarily brick-and-mortar model to an omnichannel one. The point is, whether a company has been in business five decades, five years or five months, software remains ravenous and is always looking for new companies and industries to “eat.”
Change in the face of serious threats
Facing this threat, how should corporate leadership respond? There are some excellent examples of CEOs who have galvanized their companies and led them through the massive, gut-wrenching change required to pivot in the face of a serious threat. A few of the biggest examples include:
- In 1995, it became apparent to Microsoft co-founder and then-CEO Bill Gates that the internet was “the most important single development to come along since the IBM PC,” and, if not embraced in haste, a threat to many of Microsoft’s businesses. In May of that year he published the “The Internet Tidal Wave” memo and focused all of Microsoft on adopting and building for the internet. Almost 20 years later, current Microsoft CEO Satya Nadella similarly made the bold decision to redirect the company for a cloud-first world.
- Facebook went public at $38 per share in May of 2012 but within months, stocks could be had for a little over half that. The concern? Facebook was a desktop-optimized website without a polished mobile presence, and by 2012, consumer attention had begun to accelerate towards mobile at a much higher rate than many initially predicted. Facebook CEO Mark Zuckerberg reacted by not only proclaiming Facebook a mobile-first company, but also backing up that proclamation with action.
- Turning to another company I’ve worked with via Apigee, T-Mobile launched its highly visible “Uncarrier” campaign—which offers streamlined, customer-friendly plans and services—while also investing in and executing a new IT vision dedicated to ongoing digital transformation. T-Mobile execs have credited the technology effort, spearheaded by CEO John Legere, with helping the company to introduce new services and better service customers. T-Mobile’s market cap has more than doubled since Legere took over in 2012.
Keeping pace with changing customer needs
In the face of an existential threat, strong executive leadership is required to pivot the company to safety, as these examples attest. Digital transformationisn’t about deploying new technologies just to make an existing approach more efficient or to add a few new apps or features to the status quo; digital transformation is about keeping pace with changing customer needs by leveraging software platforms to continuously evolve how the business operates. This can be akin to turning an enormous ship—and a ship can’t turn very well without her captain, first mate, and other leaders showing the way.
Research supports this. A recent Deloitte survey, for example, found that over “80 percent of respondents from digitally maturing organizations say their leaders have sufficient knowledge and ability to lead the company’s digital strategy,” compared to only “22 percent of early-stage business respondents [who] have the same belief.” Similarly, Gartner research finds that CEOs are seeking a “deeper understanding of digital business” as they shift their focus from growth in general to how technology helps them attain it.
More recently, the onslaught of software devouring the world has been further accelerated by machine learning making everything smarter, voice interfaces changing how people interact with devices, and more. To keep pace, corporate leaders need to galvanize their companies to build and deploy software faster, make systems and data easily accessible inside and outside their companies, and improve digital experiences through not only machine learning but also constant data-driven iteration.
Seven years after Andreesen’s editorial, the pace of digital disruption is still increasing, and so is the need for strong leadership to pivot fully into digital. Over half of the Fortune 500 has been acquired, merged or declared bankruptcy since 2000—and the companies that survive in coming years won’t be those whose leaders treat technology as an IT concern rather than a core part of the business.
Apigee Helps Bank BRI Rewrite its Digital Future and Achieve Financial Inclusion
6092
Of your peers have already read this article.
3:00 Minutes
The most insightful time you'll spend today!
About Bank BRI
Bank Rakyat Indonesia is one of the largest banks in Indonesia and is committed to increasing financial inclusions among un-banked Indonesians. Bank BRI specializes in using modern digital banking to facilitate microfinance lending across its network of over 10,000 branches and thousands of branchless agents.
Google Cloud Results
- Contributes $50M in revenue through the Apigee monetization feature
- Wins recognition for best digital bank in Indonesia from The Asian Banker in 2019
- Achieves ISO 27001 information security for open APIs, earning distinction as the only bank in ASEAN to receive certification to date
- Reduces partner onboarding from 6 months to under 1 hour with Apigee developer portal
Bank Rakyat Indonesia is making waves in Asia with its award-winning digital strategy. As a government-owned bank, Bank BRI is dedicated to changing the lives of its customers through accelerating financial inclusion across Indonesia. With an aggressive target of 84 percent of Indonesians participating in the banking system by 2022, Bank BRI is leapfrogging fintech competition thanks to its innovative digital strategy that has APIs at its core. By the end of 2019, Bank BRI expects to have reached a 70 percent financial inclusion rate among the country’s population, in part due to the adoption of the Cloud Apigee API Management Platform as the bank’s digital nucleus.
Transforming a legacy into a digital future
In the banking business, trust is essential, not only between the bank and its customers, but also between the bank and its partners. Recognizing that gaining and maintaining this trust would be key to customer and partner adoption of the new Bank BRI products and services, the bank decided to pursue ISO 27001 certification in 2018, becoming the first bank in ASEAN (the Association of Southeast Asian Nations) to become certified as information security compliant. Now the international community of partners and customers who use the bank’s APIs have yet another reason to place their trust Bank BRI.
“Apigee has become the central nervous system for all communications between the digital core banking, the microservices, the frontend, and the apps. Apigee has become our sun. Everything rotates around Apigee.”—Kaspar Situmorang, Executive Vice President, Bank Rakyat Indonesia
Kaspar Situmorang, Executive Vice President of Bank BRI, had the original vision for how the bank could transform itself into a fintech with digital technology and APIs. His team got started by implementing a web-native frontend over a new technology stack with Apigee as a second layer. This was a big change from the legacy technologies that existed when Situmorang joined the bank in 2017. Previously all of the bank’s products had their own public APIs, which were very difficult to manage, secure, and monetize.
Since deploying Apigee, it’s become much easier to manage the entire API lifecycle. Situmorang’s digital bank team of 15 uses the Apigee monetization and developer portal features while managing and securing APIs and conducting big data integrations. Apigee has become Bank BRI’s center of communications, handling all transactions between the bank and third parties.
Whereas previously it could take up to six months to onboard a new partner using host-to-host and VPN technology, now it takes less than an hour for partners to self-onboard using the Bank BRI Apigee developer portal. On the portal, partners can register, browse APIs, test in the sandbox, and go into production — all in less than an hour.
“Apigee has become the central nervous system for all communications between the digital core banking, the microservices, the frontend, and the apps. Apigee has become our sun. Everything rotates around Apigee,” says Situmorang.
Increasing financial inclusions
With more than 10,000 offices across Indonesia, Bank BRI has the largest network of any bank in ASEAN. The bank is also the biggest microfinance lender in the region. Though already present in even the most far-flung corners of Indonesia, Bank BRI is still working on increasing financial inclusion among un-banked Indonesians. With 56 million people that haven’t accessed banking services, Indonesia is in the bottom four countries for financial literacy in the world, along with Bangladesh, India, and China. It’s estimated that there is up to $8.3 billion in currency being held outside the banking system.
In order to reach this mostly rural, subset of the population, the bank launched Agent BRILink, a nationwide network of branchless agents. These agents can open new accounts, take deposits, pay out withdrawals, and process and disburse loans in under two minutes with the Pinang microfinance mobile app. To date, over 30,000 customers have received loans through Pinang. Handling its own risk-scoring and automatic payroll deductions for payments has translated into less risky and more profitable loans for Bank BRI.
“Customers download the app and scan their ID, capturing their credit score in just a few seconds. The digital offer letter says how much they’re approved for. They can then accept it, go to the approval screen, and do facial recognition. The money is disbursed immediately. GCP has transformed us into a fintech.”—Kaspar Situmorang, Executive Vice President, Bank Rakyat Indonesia
BRILink agents are bank customers who have been scored highly for reliability by the bank’s big data analyses and who maintain a minimum balance of around $800. Combining this data with the Google Maps API, Bank BRI is able to score all 75.5 million of its customers and identify which of them should be recruited as agents for underbanked areas. Since 2018, the bank has been able to appoint more than 200,000 branchless agents using the Agent BRILink app, eliminating the need for logistically challenging face-to-face meetings. This has resulted in an increase in loan volume from branchless business from $15 billion in 2017 to $26 billion in 2018.
To enable branchless agents to sign up new customers and provide banking services, all they need is a mobile phone and internet service. With many parts of rural Indonesia not covered by commercial 3G, Bank BRI has overcome this hurdle by operating its own satellite. With the connectivity the satellite guarantees, branchless agents can help customers obtain microfinancing and open new shops and businesses in all parts of the country. The satellite also provides internet service across the APAC region wherever the bank operates, from Sri Lanka to New Zealand. While it might seem unusual for a bank to operate a satellite, it’s reflective of Bank BRI’s commitment to reaching its financial inclusion targets and meeting its customers wherever they are.
“Pinang was created to win against fintechs trying to compete against us on speed, cost, and security,” says Situmorang. “The truth is that Indonesian regulators closed about 650 fintechs, mainly in the peer-to-peer lending space, because they were unsafe, too expensive, and very slow.”
Using APIs to create and monetize new products
Another way that Bank BRI is leveraging Google Cloud Platform solutions is through an innovative use of the Cloud Vision API, which enables the bank to integrate with the Indonesian government ID database. Identities of new customers — whether they’re coming in via a branch, a BRI Link Agent, or a mobile app — are automatically verified in seconds through facial recognition. With instant credit scoring and identity fraud concerns essentially eliminated, the bank can make more confident lending decisions.
“Monetization is very important to us. It enables us to define our pricing based on API calls and bill automatically based on usage. We’ve already recognized $50 million through the Apigee monetization feature.”—Kaspar Situmorang, Executive Vice President, Bank Rakyat Indonesia
“Customers download the app and scan their ID, capturing their credit score in just a few seconds,” explains Situmorang “The digital offer letter says how much they’re approved for. They can then accept it, go to the approval screen, and do facial recognition. The money is disbursed immediately. GCP has transformed us into a fintech.”
Bank BRI sees a bright digital future, in part thanks to the API product marketplace it’s creating to serve fintechs. With its digital technologies and massive customer base, the bank is sitting on a treasure trove of big data. Bank BRI already packages this data through more than 50 monetized open APIs for more than 70 ecosystem partners wanting to do credit scoring, business assessments, and risk management. Fintechs, insurance companies, and financial institutions don’t have the talent or the financial resources to do quality credit scoring and fraud detection on their own, so they are turning to Bank BRI.
“Monetization is very important to us. It enables us to define our pricing based on API calls and bill automatically based on usage. We’ve already recognized $50 million through the Apigee monetization feature,” says Situmorang.
Bank BRI is meeting and surpassing the goals it has set for itself for digitalization, increasing financial inclusion, and creating new revenue streams with APIs.
How This Leading Trading Company Uses APIs to Build Fintech Apps Quickly and Cost-Effectively
4603
Of your peers have already read this article.
5:10 Minutes
The most insightful time you'll spend today!
Tradier uses the Apigee API management platform from Google to abstract the legacy complexities of capital markets so that developers can build FinTech applications in an agile, nimble, and quick fashion at minimal cost. The company embodies the evolution of what cloud technology can enable in the form of an API-first business delivered as a service.
The rise of API-powered FinTech
Historically, companies that wanted to build systems, applications, or services to interact with the stock market would have to build an entire brokerage operation from scratch. This would include data infrastructure, compliance infrastructure, and storage capabilities. It could take years and massive capital expense to accomplish everything that was required to be ready to serve customers.
Tradier provides this infrastructure as an API-based service so that the same companies can launch investor applications in as little as a few weeks. This democratized access means that FinTech innovation can come from anywhere, giving the same opportunities to create new products to everyone, from enterprise customers to startups.
“Financial markets are becoming fundamentally decentralized and unbundled,” says Dan Raju, co-founder, CEO, and chairman at Tradier. “The services that large legacy banks and brokerage firms used to offer are being supplanted by Tradier’s microservices and APIs, which power innovation.”
More than 200 companies use Tradier to develop and launch new products, or to add new features and functions that they traditionally would not have offered in existing products. With a large and diverse user base, Tradier faced the challenge of managing its partners in way that helps ensure it can grant credentials, track, monitor, and report in an efficient and equitable manner.
At the same time, the company recognized the inherent value of its partners for their power to leverage Tradier APIs to innovate. Tradier’s fundamental market disruption is the partner ecosystem, where the company is engaged along with its partners to deliver value to the entire ecosystem in the form of new products and services.
Embracing an API-powered ecosystem
Tradier has moved beyond providing great APIs toward engaging its ecosystem. If a customer wants a specific dataset, the company doesn’t automatically build a new product. Instead, Tradier looks to the ecosystem to build the product. With this approach, Tradier has taken its capabilities and multiplied them by hundreds.
“The fundamental difference between thinking about an API ecosystem versus an API product is the difference between being a participant who’s enabling innovation and not just a company delivering a set of technical capabilities,” Raju says.
Tradier takes an outside-in approach toward engaging its API ecosystem. Constantly listening to participants and helping to enable and empower them to create value is fundamental to the company’s business model. Rather than simply focusing on building new capabilities on its own, Tradier listens to what functionalities customers need and facilitates development. In many cases, the ecosystem generates the requested product organically rather than Tradier needing to do it.
“I love APIs because they allow you to empower others to create value. The concept of empowering others to create value along with you is what is the most satisfying, and the most fascinating, thing about APIs,” says Raju.
Delivering value at scale
Tradier handles between 500 million to 1 billion API calls and a billion dollars in transactions a month, and all of them run through the Apigee API management platform. Apigee’s last mile forms the single layer that manages Tradier’s infrastructure, including security, analytics, developer interactions, and execution. The company also uses Apigee to comply with an array of regulatory reporting, mandated by Tradier’s status as a FINRA (Financial Industry Regulatory Authority)-regulated entity.
“Apigee is integral to the Tradier offering. They have been great partners and have always collaborated and enabled us to innovate at a pace that helped Tradier attract developers and innovative companies. We see tremendous potential in the synergy of Apigee and Google as it brings to the market a vast extended capability set based on the Google Cloud Platform.”
Tradier is an API-centric ecosystem that delivers value to an entire set of players where the nucleus is the Apigee API management suite, which helps deliver, innovate, publish, manage, monitor, and secure the ecosystem on a day-to-day basis. Simplicity combined with product evangelism is the key to success in the API space, Raju says.
Tradier’s capabilities to innovate, iterate, and travel the journey with its customers, partners, and developers has yielded many rewards. The company’s long history of working with Apigee has enabled it to assemble a set of people and resources for creating engagement, as well as to create a winning set of APIs for delivering FinTech capabilities.
Considering the transformative future
Looking toward a future in which the financial services industry will experience ongoing disruption, Raju predicts that Tradier will continue to leverage APIs to lead the way.
“I think traditional banks are under attack. They are being replaced by a set of nimble, agile players that are offering a lot of new functionality to customers. This is forcing banks to think about how they can digitize their products through APIs so that they can provide the same functionalities as newer players.”
With companies like Tradier and others offering functionality that used to be in-house and exposing it outside, traditional brokerage firms are also being forced to rethink their model. Raju believes that this line of thinking also extends to the Blockchain.
“Exposing Blockchain-like capabilities through APIs is going to be a disruptive influence, and it will be critical for companies to think about how APIs, and more importantly Blockchain, can create value for us.”
3578
Of your peers have already downloaded this article
2:30 Minutes
The most insightful time you'll spend today!
After undergoing an agile transformation, ING realized it needed a standardized platform to support the work their developers were doing. “Our DevOps teams got empowered to be autonomous,” says Thijs Ebbers, Infrastructure Architect.
“It has benefits, you get all kinds of ideas. But a lot of teams are going to devise the same wheel. Teams started tinkering with Docker, Docker Swarm, Kubernetes, Mesos. Well, it’s not really useful for a company to have one hundred wheels, instead of one good wheel,” Ebbers added.
Using Kubernetes for container orchestration and Docker for containerization, the ING team began building an internal public cloud for its CI/CD pipeline and green-field applications. The pipeline, which has been built on Mesos Marathon, will be migrated onto Kubernetes.
The bank-account management app Yolt in the U.K. (and soon France and Italy) market already is live hosted on a Kubernetes framework. At least two greenfield projects currently on the Kubernetes framework will be going into production later this year. By the end of 2018, the company plans to have converted a number of APIs used in the banking customer experience to cloud-native APIs and host these on the Kubernetes-based platform.
“Cloud native technologies are helping our speed, from getting an application to test to acceptance to production,” says Infrastructure Architect Onno Van der Voort. “If you walk around ING now, you see all these DevOps teams, doing stand-ups, demoing. They try to get new functionality out there really fast.”
Find out how.
More Relevant Stories for Your Company
Scaling with Breaking News: BBC’s Serverless Infrastructure on Google Cloud
Editors note: Today's post is from Neil Craig at the British Broadcasting Corporation (BBC), the national broadcaster of the United Kingdom. Neil is part of the BBC’s Digital Distribution team which is responsible for building the services such as the public-facing www bbc.co.uk and .com websites and ensuring they are
Google Cloud Partnership Helps Lowe’s SRE Team Achieve 20X More Releases Per Month
Editor’s note: Today we hear from the Lowe’s SRE team. They share about how they have been able to increase the number of releases they can support by adopting Google’s Site Reliability Engineering (SRE) framework and leveraging their partnership with Google Cloud. At Lowe’s, we’ve made significant progress in our multiyear technology transformation.
Private Services Connect in Google Cloud Regions Enables Customers to Consume Services Faster
At Google Cloud, we believe in making it simple and secure to consume services whether they're from Google, a third party or customer-owned. With Private Service Connect, we have adopted a service-centric approach to our network that abstracts the underlying networking infrastructure. And today, we are announcing Private Service Connect is
App Engine Basics to Help You Build and Deploy Low-latency, Scalable Apps
App Engine is a fully managed serverless compute option in Google Cloud that you can use to build and deploy low-latency, highly scalable applications. App Engine makes it easy to host and run your applications. It scales them from zero to planet scale without you having to manage infrastructure. App
