Software Engineering Project for CSC 510

Sync Ends is an automated bridge to sync service owners and service consumers. Every team has a single Postman collection that they use to test their APIs and share it across in their documentations. The backend team has to register their service on our application and we take care of the rest. Everytime there is a change in the way the API is called, we parse the changes and inform the API consumers. This way all the team members are informed about the changes and know exactly what to edit in their codebase. The Slack framework lets you concentrate on the core functionality you want to build without worrying about integration overheads.

• Architecture Diagram
• Features
• Patterns in the code
• Documentation
  • What is Sync Ends?
  • Why use Sync Ends?
  • How to use Sync Ends?
    • Installation
    • Usage
      • How to write the config_file? (format of the file should be .json)
    • What happens after this command is run?
• Experimentation Phase for Project 3
  • It vs Not It
  • Idea for the Experimentation
  • Experimentation SetUp
    • Step 1 : Setup Postman
    • Step 2 : Create a Slack workspace and integrate Slack bot
      • 2a. Creating Slack workspace
      • 2b. Creating Slack bot
  • Experimentation Process
  • Experimentation Measures
    • Quantitative measures
    • Qualitative measures
• How to Contribute?
• License

• We are using Composite and Layer pattern in the code. The Parser module parses the user input and passes the parsed data to the underlying layers. The sync end service accepts the data from the parser layer and sends the notification to Slack.
• The Collection object uses the Composite pattern where a Collection contains multiple EndPoints and each End Point has attributes such as URL, method type, name, etc.

Please have a look at the point descriptions of each function/class through this documentation file generated via pdoc3. To view this documentation, clone the repository and then open the linked file in the browser.

Sync ends is a productivity service that focuses on saving developer time by automating API changes to their consumers in real-time thus improving your team's productivity. Consider an API consumer using multiple APIs in their system. In this ever-changing world, it is impossible for the consumer to be updated with each and every API change. This is the problem that Sync Ends service addresses. The service is easy to install and this reduces the communication overhead on side of the API devs. So avoid crashes and jump on the Sync Ends bandwagon! :)

This version of sync ends is highly usable as it can be simply downloaded through PyPI. It is a single package which satisfies all your needs with clean documentation. Using just a simple config file, you can start the service from terminal through our CLI interface. All your API's from the Postman collection will be fetched and their changes will be reflected as notifications in your slack channel.

Transcript(Hindi to English) - API can change anytime

Reference : Meme From TV Series Mirzapur

pip install sync-ends

The code is deployed as a python package on PyPI which is a single step installation process.

1. The package is primarily run through a CLI (single step) for ease of use.

Run the following command with required parameters.

syncends  --config_file </path/to/your/local/config/file>

What is --config_file?

config_file - the configuration file used by the Sync Ends service

{
    "postman_api_key": "<a>",
    "slack_token": "<b>",
    "trigger_interval": <c>,
    "collections": [
        {
            "collection_name": "<d>",
            "slack_channel": "<e>"
        }
    ]
}

where,

• a: postman api key generated using steps shown in postman setup section
• b: slack token generated using steps shown in slack setup section
• c: [optional: default=10] time (in seconds), after which application will periodically check for api changes
• d: collection name from postman collections
• e: [optional: default="general"] slack channel in which notifications will be sent (must be a public channel)

This command is the entry point to a background process which fetches all the Postman collections using the Postman API key and posts a message through the Slack bot token configured in the Slack channel specified. The background service fetches the Postman collections every trigger interval seconds. Since all of this happens automatically after running the CLI command, this means that developer on changing the API in the Postman does not have to worry about notifying any API consumers of the change. That magic is done by our bot :)

Each experiment will involve 2 subjets:

• One person will act as API Developer
• 2^nd person will act as API Consumer. (Also referred to as API Tester at some places)

In the experiment phase, we will be planning to evaluate the performance improvement of the API consumer (tester) in a rapidly developing environment. The experiment is planned to be run in pairs where one person will act as a developer and the other will act as an API consumer (tester).

• The job of the developer will be to change API schemas in Postman which mocks the behaviour that a change has been made in the serving of API in the actual codebase.
• The job of the tester will be to monitor these changes and note them down which mocks the behaviour that the API consumer is now aware that a change needs to be made in the codebase where this API is used.

In the presence of our Sync Ends service, once the developer makes a change in the APIs in the Postman collection, the changes will be directly fetched from Postman and a Slack message will be sent in the channel with a detailed diff notifying the API consumer of this change.

In the absence of our service, the developer will have to manually notify changes to the API consumer and if the developer forgets to do so, the API consumer will be unaware of API changes and this would mock the fact that the API consumer will have a crash when their application tries to call the updated API with old parameters.

The primary idea for the experiment is to provide the participants(lab rats) with a clear setup for interaction with the service. As we mentioned, the experiment is planned to be run in pairs. As a result, the team picking up this project will simply need to configure following things:

• A general Postman account with a single collection but multiple APIs. (steps)
  • The developer half of the lab rats will interact with this Postman account where they will change APIs and our Sync Ends service will take care of the rest.
  • The login credentials and api key of the postman account will need to shared with the API Developers. So please create an account(s) keeping that in mind.
• A Slack channel along with configuring a Slack Bot which interacts with our Sync Ends service. (steps)
  • For the tester half of lab rats, they will need to be added to this channel.

We leave it upto the team picking up this project to define whether they will add all pairs of participants in a common Slack channel or make multiple Slack channels for different experiments. The same goes for the Postman Collection part.

The experiment will have two phases. (1) A pair of people NOT using our system and performing the experiment (2) The same pair of people now using our system and performing the experiment. This would ensure that the same group of people who experienced the absence can now, hopefully, understand the importance of the Sync Ends service and can benefit from it.

To get an even better read on the effectiveness of the system, the roles of the developer and tester(API consumer) can be swapped and the experiment begin again so that both the lab rats can experience the halves and you can get a larger sample size to prove the validity of the observations.

Rest Assured, the Experimentation Setup section defines clear and precise steps to get done with the setup part. In our view and based on our own preliminary trial, it will be easier for the team to just make a single Postman collection from the sample collection schema provided and add lab rats to and remove them from a common Slack channel. However, the final say is left upto the team conducting this experiment.

As mentioned above, the team needs to setup 3 things for the experiment: (1) a Postman collection (2) a Slack channel (3) a config json.

The team will have to provide the config json file and a Postman account to each API developer so that they can:

• change the API schemas in the collection
• and the sync ends service which is run would parse the changes based on the parameters in the config file.

The API developer will only need to have Python installed as our package is hosted on PyPI and will be able to access Web Postman. In the presence of our system, the developer won't have to be added to any Slack channels as that is handled by our service. However, in the absence of our system, the developer will need to have some way to communicate with API consumer, probably Slack and hence would need to be added the Slack channel where the API consumer is also added.

The API consumer(tester) will only need to be added to the Slack channel and the tester's job is to simply identify changes in APIs through Slack messages or otherwise.

1. Sign in to Postman. You can use your existing postman account but since you will need to share API key and login credentials with the API Developer, we suggest creating a new account.
2. If you do not have any pre-exiting collections on Postman, import this sample collection.
3. To integrate with the Sync Ends service, a Postman API key is required. Generate API key by visiting this page.
4. Copy the generated API key. This is required during the time of execution of the service. Make sure you store it safely as you won't be able to view this any other time.

1. Open https://slack.com/.
2. Provide your email ID. Select Create New workspace.
3. Check your email and enter the code to verify your email.
4. Provide your name and set a password.
5. Add some details to your workspace in the next page.
6. Provide a company name.
7. Workspace URL should be unique. Also remember this URL, this is what is used to login to your Slack instance.
8. Agree with the terms.
9. Skip the invite step.
10. You are up and running with your own instance of Slack.

1. Open your <workspace-URL>/apps (the one you created above). For example, https://test-visual.slack.com/apps.
2. Search for bot in the search bar and select Bots.
3. In the Bots landing page, click on Add configuration.
4. Provide a Bot name. For example, wolfpack-bot and click on Add Bot integration.
5. In the Setup instruction page: Copy and store the API Token. For example, the token may look something like this: xoxb-22672546-n1X9APk3D0tfksr81NJj6VAM.
6. Save the Bot integration.

The experimentation process for developers consists of them performing roughly these tasks:

• Adding a new API request to the collection
• Deleting a API from the collection
• Updating the name of an API
• Updating the URL of an API
• Updating the API method (GET, POST, etc.) of an API
• Updating the authentication method in the API
• Performing these steps quickly and in succession

The experimentation process for testers(API consumers) consists of them simply noting these changes in a spreadsheet that can be shared with them. Their primary job will be to note what changed in the APIs in the presence and absence of our Sync Ends service.

Throught the experiments, the teams can take following quantitative and qualitative measures:

These measures can be used to compare the results between environment with and without Sync Ends.

1. Number of APIs changed by the developer
2. Number of APIs added by the developer
3. Number of APIs deleted by the developer
4. Time taken by API consumer (tester) to identify these change/addition/deletion (In presence of the Sync Ends system v/s Without the system)

Apart from quantitative measures, these qualititive measures can be taken to identify the performance of the system:

1. How easy it is for API consumer to find the changes (In presence of the Sync Ends system v/s Without the system)
2. Can the API consumer get occupied in his personal work and still get to know about the API changes quickly?

Please take a look at our CONTRIBUTING.md where we provide instructions on contributing to the repo and help us in enhancing the product.

This project is licensed under the MIT License.