Full Stack JavaScript Strategies

Chapter 5. Third-Party Services

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 5th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the author at [e-mail].

There will come a point in developing a product when you’ll need to use a third-party service. Third-party services offer complex or proprietary functionality that exists outside your codebase and your company. The third-party service is usually managed by another company; you pay a fee to use it and have access to support when things go wrong.

Third-party services come up when you need functionality that would take a significant amount of time to implement, would be difficult to maintain, and would likely need its own team, such as payment systems, authentication/authorization, and monitoring and logging for your app.

In this chapter, we’ll go over:

• Choosing third-party services

• Implementing a third-party service in your system

• Managing errors, outages, and upgrades

Working with third-party services is going to come up at some point, so it’s best to go in with an idea of what you’re getting into. Usually, the third-party service provides an API or software ...