Developing a document service

In the previous section, we outlined an architecture for our serverless application. During this analysis phase, we worked out the high-level components required and then theorized on the type of activities required. Creating a document service requires the creation of a Cloud Run service to consume information from a Cloud Pub/Sub subscription. As we have chosen to minimize the code development process, our productivity has been significantly increased. Code for complex notifications and message queues has been deferred to existing mechanisms managed by Google Cloud. Instead, we will concentrate on building only the specific element needed for our requirements, for example, PDF conversion.