Full Stack JavaScript Strategies

Chapter 26. Integration Concerns

You’ve gone through the process of getting the full stack app to production, and everything seems to be working smoothly. Getting the app to production isn’t a small feat, and you now have a good baseline to work from, so you can start looking at areas that can be improved. This is when you can really stress-test the app to see how well the frontend and backend are connected and how the third-party services really behave.

As you and other teams start to poke at the app in production, a number of concerns will come up. Some will be surprises to everyone, no matter how much planning you do. Someone might notice they don’t have access to a certain page or there’s an unexpected glitch on the frontend. While you and the team have done all you can to test everything in a preproduction environment, some things will just behave differently. This is where you start to hammer out those things you couldn’t test for in any other environment.

In this chapter, I’ll go over:

• Frontend and backend concerns

• Things you should check for with your third-party services

• Data and security management in production

• Containerization of your app

This is a point in the development lifecycle that takes grit and perseverance because you’re so close to being done! These last integration concerns are what will help you, the team, and everyone else know that you can automate your deployments with confidence that they will work consistently. Before, you were able to develop ...