At Salesforce, we want to ensure all our experiences meet or exceed current WCAG (Web Content Accessibility Guidelines) standards. These accessibility guidelines, while comprehensive, can be overwhelming to absorb. They’re also open to interpretation. A group of engineers and designers across our accessibility and design systems teams partnered to evaluate the latest WCAG color contrast guidelines and streamline standards for our work. We wanted to fully integrate WCAG and hope our process can inspire your teams to do the same.

To leverage the scale and agility of the public cloud, we have built a new generation of infrastructure platform for Salesforce.

A framework prescribing the minimal set of indicators that every service needs to discern its health and performance.

By introducing a plug-in-like architecture, we could reshape how teams contribute native features to our mobile app.

There are three categories of monitoring design patterns that can help solve commonly occurring problems in software development.

We implemented a three-pronged strategy for the Salesforce Commerce APIs: monitoring, continous testing, and alerting.

We analyzed user email open and click behaviors across hundreds of billions of emails to build an algorithm for send time optimization.

How we built a multi-tenant, omnichannel inventory availability solution that is highly available, performant, and highly accurate.

What if you could dramatically reduce the cost to operate on cloud providers? That’s what we found when we dug into Redis HASH vs SET.

A purpose-built solution for producing eventually consistent data replicas.

Complementing Salesforce’s Record Access Control Mechanism.

At Dreamforce in 2017, Salesforce introduced personalized theming and branding into our product. Customers could add their logo and brand…

What happens when your hybrid app suffers from memory problems without any obvious symptoms? How does one begin to measure them?

Metadata can be a bit of a nebulous term, so let’s start by talking about what it really means.

Everything a computer works with is data — ones and zeros — from the firmest firmware to the most ephemeral state of a pixel on the screen. By metadata, however, I’m talking specifically about data that describes or constrains the behavior of software. It’s what tells us that this byte is an instruction in the OS, and that byte is one pixel in a catchy song about cheeseburgers.

Now, let’s clear something up right away: by “metadata”, I specifically don’t mean just “additional data”, like a timestamp, or a browser fingerprint. It’s certainly not uncommon to hear people use the word that way (“I want to know what metadata these fast food companies are collecting about me …”), but that’s not at all what I’m talking about here. That’s “meta” if you’re talking about the original Greek sense of the word (“beyond”), since things like this are beyond what we usually see in the user interface. But you probably weren’t talking about the original Greek sense of the word, were you? No. So for the purposes of this article, let’s go with my definition: metadata is data that alters the behavior of software.

The idea of a single root cause does not reflect reality. This piece explains a critique of root cause analysis and presents a better idea.

为什么to SMB纷纷转to KA？