[x/go.dev] _content: correct various typographical problems for Goldmark
americanexpress: The possessive of American Express is American Express's, with a final s. The final s is only dropped for possessive plurals, like the Smiths' house. Goldmark also doesn't convert the trailing ' correctly, so this makes the tree safer for Goldmark. cloud: The GoKit URL clearly does not end in [. google: The leading - looks like a single-element list in Markdown. Change it to an em dash, which is more appropriate anyway. Change-Id: I34beffaacef333ee7931c24b2b3503532d2e9de1 X-GoDev-Commit: fbb61a60c4e900e3151b46064bfd66b10041bad3
This commit is contained in:
Russ Cox
Родитель
880e05383c
Коммит
2ad8fbcc04
|
|
@ -28,7 +28,7 @@ American Express’ payment processing systems have been developed over its long
|
|||
|
||||
### Modernizing American Express systems
|
||||
|
||||
American Express understands that the programming language landscape is changing drastically. The company's existing systems were purpose-built for high concurrency and low latency, but knowing that those systems would be re-platformed in the near future. The payments platform team decided to take the time to identify what languages were ideal for American Express' evolving needs.
|
||||
American Express understands that the programming language landscape is changing drastically. The company's existing systems were purpose-built for high concurrency and low latency, but knowing that those systems would be re-platformed in the near future. The payments platform team decided to take the time to identify what languages were ideal for American Express's evolving needs.
|
||||
|
||||
The payments and rewards platform teams at American Express were among the first to start evaluating Go. These teams were focused on microservices, transaction routing, and load-balancing use cases, and they needed to modernize their architecture. Many American Express developers were familiar with the language’s capabilities and wanted to pilot Go for their high concurrency and low latency applications (such as custom transactional load balancers). With this goal in mind, the teams began lobbying senior leadership to deploy Go on the American Express payment platform.
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ The payments and rewards platform teams at American Express were among the first
|
|||
|
||||
For their assessment, Cane's team chose to build a microservice in four different programming languages. They then compared the four languages for speed/performance, tooling, testing, and ease of development.
|
||||
|
||||
For the service, they decided on an ISO8583 to JSON converter. ISO8583 is an international standard for financial transactions, and it’s commonly used within American Express' payment network. For the programming languages, they chose to compare C++, Go, Java and Node.js. With the exception of Go, all of these languages were already in use within American Express.
|
||||
For the service, they decided on an ISO8583 to JSON converter. ISO8583 is an international standard for financial transactions, and it’s commonly used within American Express's payment network. For the programming languages, they chose to compare C++, Go, Java and Node.js. With the exception of Go, all of these languages were already in use within American Express.
|
||||
|
||||
From a speed perspective, Go achieved the second-best performance at 140,000 requests per second. Go showed that it excels when used for backend microservices.
|
||||
|
||||
|
|
@ -72,7 +72,7 @@ American Express is just beginning to see the benefits of Go. For example, Go wa
|
|||
|
||||
Go’s garbage collection is also a major improvement over other languages, both in terms of performance and ease of development. “We saw far better results of garbage collection in Go than we did in other languages, and garbage collection for real time transaction processing is a big deal.” says Cane. “Tuning garbage collection in other languages can be very complicated. With Go you don’t tune anything.”
|
||||
|
||||
To learn more, read ["Choosing Go at American Express"](https://americanexpress.io/choosing-go/) which goes into more depth about American Express' Go adoption.
|
||||
To learn more, read ["Choosing Go at American Express"](https://americanexpress.io/choosing-go/) which goes into more depth about American Express's Go adoption.
|
||||
|
||||
### Getting your enterprise started with Go
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ Go's strengths shine when it comes to building services. Its speed and built-in
|
|||
|
||||
Go has a strong ecosystem supporting service development. The [standard library](https://golang.org/pkg/) includes packages for common needs like HTTP servers and clients, JSON/XML parsing, SQL databases, and a range of security/encryption functionality, while the Go runtime includes tools for [race detection](https://golang.org/doc/articles/race_detector.html), [benchmarking](https://golang.org/pkg/testing/#hdr-Benchmarks)/profiling, code generation, and static code analysis.
|
||||
|
||||
The major Cloud providers ([GCP](https://cloud.google.com/go/home), [AWS](https://aws.amazon.com/sdk-for-go/), [Azure](https://docs.microsoft.com/en-us/azure/go/)) have Go APIs for their services, and popular open source libraries provide support for API tooling ([Swagger](https://github.com/go-swagger/go-swagger)), transport ([protocol buffers](https://github.com/golang/protobuf), [gRPC](https://grpc.io/docs/quickstart/go/)), monitoring ([OpenCensus](https://godoc.org/go.opencensus.io)), Object-Relational Mapping ([gORM](https://gorm.io/)), and authentication ([JWT](https://github.com/dgrijalva/jwt-go)). The open source community has also provided several service frameworks, including [Go Kit](https://gokit.io/[), [Go Micro](https://micro.mu/docs/go-micro.html), and [Gizmo](https://github.com/nytimes/gizmo), which can be a great way to get started quickly.
|
||||
The major Cloud providers ([GCP](https://cloud.google.com/go/home), [AWS](https://aws.amazon.com/sdk-for-go/), [Azure](https://docs.microsoft.com/en-us/azure/go/)) have Go APIs for their services, and popular open source libraries provide support for API tooling ([Swagger](https://github.com/go-swagger/go-swagger)), transport ([protocol buffers](https://github.com/golang/protobuf), [gRPC](https://grpc.io/docs/quickstart/go/)), monitoring ([OpenCensus](https://godoc.org/go.opencensus.io)), Object-Relational Mapping ([gORM](https://gorm.io/)), and authentication ([JWT](https://github.com/dgrijalva/jwt-go)). The open source community has also provided several service frameworks, including [Go Kit](https://gokit.io/), [Go Micro](https://micro.mu/docs/go-micro.html), and [Gizmo](https://github.com/nytimes/gizmo), which can be a great way to get started quickly.
|
||||
|
||||
### Go tools for Cloud Computing
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Reliability Engineering (SRE), a role that many other companies have since adopt
|
|||
Our mission is to protect, provide for, and progress the software and systems
|
||||
behind all of Google’s public services with an ever-watchful eye on their
|
||||
availability, latency, performance, and capacity.”
|
||||
- [Site Reliability Engineering (SRE)](https://sre.google/).
|
||||
— [Site Reliability Engineering (SRE)](https://sre.google/).
|
||||
|
||||
{{backgroundquote `
|
||||
quote: |
|
||||
|
|
|
|||
|
|
@ -205,7 +205,7 @@
|
|||
|
||||
<h3 id="modernizing-american-express-systems">Modernizing American Express systems</h3>
|
||||
|
||||
<p>American Express understands that the programming language landscape is changing drastically. The company’s existing systems were purpose-built for high concurrency and low latency, but knowing that those systems would be re-platformed in the near future. The payments platform team decided to take the time to identify what languages were ideal for American Express’ evolving needs.</p>
|
||||
<p>American Express understands that the programming language landscape is changing drastically. The company’s existing systems were purpose-built for high concurrency and low latency, but knowing that those systems would be re-platformed in the near future. The payments platform team decided to take the time to identify what languages were ideal for American Express’s evolving needs.</p>
|
||||
|
||||
<p>The payments and rewards platform teams at American Express were among the first to start evaluating Go. These teams were focused on microservices, transaction routing, and load-balancing use cases, and they needed to modernize their architecture. Many American Express developers were familiar with the language’s capabilities and wanted to pilot Go for their high concurrency and low latency applications (such as custom transactional load balancers). With this goal in mind, the teams began lobbying senior leadership to deploy Go on the American Express payment platform.</p>
|
||||
|
||||
|
|
@ -215,7 +215,7 @@
|
|||
|
||||
<p>For their assessment, Cane’s team chose to build a microservice in four different programming languages. They then compared the four languages for speed/performance, tooling, testing, and ease of development.</p>
|
||||
|
||||
<p>For the service, they decided on an ISO8583 to JSON converter. ISO8583 is an international standard for financial transactions, and it’s commonly used within American Express’ payment network. For the programming languages, they chose to compare C++, Go, Java and Node.js. With the exception of Go, all of these languages were already in use within American Express.</p>
|
||||
<p>For the service, they decided on an ISO8583 to JSON converter. ISO8583 is an international standard for financial transactions, and it’s commonly used within American Express’s payment network. For the programming languages, they chose to compare C++, Go, Java and Node.js. With the exception of Go, all of these languages were already in use within American Express.</p>
|
||||
|
||||
<p>From a speed perspective, Go achieved the second-best performance at 140,000 requests per second. Go showed that it excels when used for backend microservices.</p>
|
||||
|
||||
|
|
@ -254,7 +254,7 @@
|
|||
|
||||
<p>Go’s garbage collection is also a major improvement over other languages, both in terms of performance and ease of development. “We saw far better results of garbage collection in Go than we did in other languages, and garbage collection for real time transaction processing is a big deal.” says Cane. “Tuning garbage collection in other languages can be very complicated. With Go you don’t tune anything.”</p>
|
||||
|
||||
<p>To learn more, read <a href="https://americanexpress.io/choosing-go/" rel="noreferrer" target="_blank">“Choosing Go at American Express”</a> which goes into more depth about American Express’ Go adoption.</p>
|
||||
<p>To learn more, read <a href="https://americanexpress.io/choosing-go/" rel="noreferrer" target="_blank">“Choosing Go at American Express”</a> which goes into more depth about American Express’s Go adoption.</p>
|
||||
|
||||
<h3 id="getting-your-enterprise-started-with-go">Getting your enterprise started with Go</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -238,7 +238,7 @@
|
|||
|
||||
<p>Go has a strong ecosystem supporting service development. The <a href="https://golang.org/pkg/" rel="noreferrer" target="_blank">standard library</a> includes packages for common needs like HTTP servers and clients, JSON/XML parsing, SQL databases, and a range of security/encryption functionality, while the Go runtime includes tools for <a href="https://golang.org/doc/articles/race_detector.html" rel="noreferrer" target="_blank">race detection</a>, <a href="https://golang.org/pkg/testing/#hdr-Benchmarks" rel="noreferrer" target="_blank">benchmarking</a>/profiling, code generation, and static code analysis.</p>
|
||||
|
||||
<p>The major Cloud providers (<a href="https://cloud.google.com/go/home" rel="noreferrer" target="_blank">GCP</a>, <a href="https://aws.amazon.com/sdk-for-go/" rel="noreferrer" target="_blank">AWS</a>, <a href="https://docs.microsoft.com/en-us/azure/go/" rel="noreferrer" target="_blank">Azure</a>) have Go APIs for their services, and popular open source libraries provide support for API tooling (<a href="https://github.com/go-swagger/go-swagger" rel="noreferrer" target="_blank">Swagger</a>), transport (<a href="https://github.com/golang/protobuf" rel="noreferrer" target="_blank">protocol buffers</a>, <a href="https://grpc.io/docs/quickstart/go/" rel="noreferrer" target="_blank">gRPC</a>), monitoring (<a href="https://godoc.org/go.opencensus.io" rel="noreferrer" target="_blank">OpenCensus</a>), Object-Relational Mapping (<a href="https://gorm.io/" rel="noreferrer" target="_blank">gORM</a>), and authentication (<a href="https://github.com/dgrijalva/jwt-go" rel="noreferrer" target="_blank">JWT</a>). The open source community has also provided several service frameworks, including <a href="https://gokit.io/[" rel="noreferrer" target="_blank">Go Kit</a>, <a href="https://micro.mu/docs/go-micro.html" rel="noreferrer" target="_blank">Go Micro</a>, and <a href="https://github.com/nytimes/gizmo" rel="noreferrer" target="_blank">Gizmo</a>, which can be a great way to get started quickly.</p>
|
||||
<p>The major Cloud providers (<a href="https://cloud.google.com/go/home" rel="noreferrer" target="_blank">GCP</a>, <a href="https://aws.amazon.com/sdk-for-go/" rel="noreferrer" target="_blank">AWS</a>, <a href="https://docs.microsoft.com/en-us/azure/go/" rel="noreferrer" target="_blank">Azure</a>) have Go APIs for their services, and popular open source libraries provide support for API tooling (<a href="https://github.com/go-swagger/go-swagger" rel="noreferrer" target="_blank">Swagger</a>), transport (<a href="https://github.com/golang/protobuf" rel="noreferrer" target="_blank">protocol buffers</a>, <a href="https://grpc.io/docs/quickstart/go/" rel="noreferrer" target="_blank">gRPC</a>), monitoring (<a href="https://godoc.org/go.opencensus.io" rel="noreferrer" target="_blank">OpenCensus</a>), Object-Relational Mapping (<a href="https://gorm.io/" rel="noreferrer" target="_blank">gORM</a>), and authentication (<a href="https://github.com/dgrijalva/jwt-go" rel="noreferrer" target="_blank">JWT</a>). The open source community has also provided several service frameworks, including <a href="https://gokit.io/" rel="noreferrer" target="_blank">Go Kit</a>, <a href="https://micro.mu/docs/go-micro.html" rel="noreferrer" target="_blank">Go Micro</a>, and <a href="https://github.com/nytimes/gizmo" rel="noreferrer" target="_blank">Gizmo</a>, which can be a great way to get started quickly.</p>
|
||||
|
||||
<h3 id="go-tools-for-cloud-computing">Go tools for Cloud Computing</h3>
|
||||
|
||||
|
|
|
|||
|
|
@ -204,7 +204,7 @@ Reliability Engineering (SRE), a role that many other companies have since adopt
|
|||
Our mission is to protect, provide for, and progress the software and systems
|
||||
behind all of Google’s public services with an ever-watchful eye on their
|
||||
availability, latency, performance, and capacity.”
|
||||
- <a href="https://sre.google/" rel="noreferrer" target="_blank">Site Reliability Engineering (SRE)</a>.</p>
|
||||
— <a href="https://sre.google/" rel="noreferrer" target="_blank">Site Reliability Engineering (SRE)</a>.</p>
|
||||
|
||||
<div class="BackgroundQuote">
|
||||
<p class="BackgroundQuote-body">
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче