VSCode is a lightweight but powerful source code editor. It comes with built-in support for JavaScript and Node.js that makes it perfect for implementing the applications of the ApplicationLayer. VSCode is available for Linux, Windows and Mac.
Step-by-Step Guidelines
Documentation
All ApplicationOwners and ApplicationImplementers need an own GitHub account and local installations of Git and VSCode from beginning on.
To build the ApplicationLayer Microservice architecture , multiple developers collaboratively works in a same or separate application implemetation.
Git allows to easily manage changes to projects, track different versions of source code, and collaborate on any section of similar code without creating conflicting issues with proposed changes.
GitHub is a cloud based versioning system for sharing code in open source projects.
Git is for keeping local data in synch with GitHub.
Git is available for Linux, Windows and Mac.
Concepts
Step-by-Step Guidelines
- Creating an own GitHub account
- Installing Git
- Activating YAML validation on your respository
- Defining CodeOwners on your respository
Code collaboration is the process of working on the code with a team.
Good collaboration processes and detailed guidelines are required for efficiently growing the application layer.
VSCode has integrated source control management and includes Git support out-of-the-box.
So, code collaboration can be managed through VSCode with the support of the Git extension.
Concepts
- Workflow for contributing
- Workflow for collaborating code
- Formulating Commit and Merge Request Messages
- Managing Conflicts
- Avoiding Conflicts
Step-by-Step Guidelines
- Setting the Proxy on TEF laptop
- Connecting VS Code with a GitHub repository
- Documenting an Issue
- Processing an Issue
- Creating a Commit
- Completing an Issue
All ApplicationOwners and ApplicationImplementers are very much invited to propose corrections and completions on the ApplicationPattern (by creating Issues) or its guidelines by addressing pull requests.
All documentation, readme and issues on GitHub are edited in MarkDown syntax. Mastering MarkDown is a precondition.
Documentation
While using Postman for writing the OpenApiSpecification, it is only a few clicks to create a dummy server (mock), which is simulating the API. The mock helps verifying correctness of the specification.
Anyway, Postman is needed for writing the TestCases.
A Postman account is for free.
All ApplicationOwners need an own Postman account.
Step-by-Step Guidelines
Documentation
Automated code generation requires syntactically well defined specifications.
OpenAPI Specification (formerly Swagger Specification) has been choosen for describing REST APIs.
Indent based YAML format has been choosen for formatting the OAS coding.
Mastering OpenAPI Specification 3.0 in YAML is a precondition.
Documentation
Concepts
LOADfiles are written in JSON. Reading through existing examples is probably the easiest way of learning the necessary structures and formats.
LOADfiles are of several thousands of lines. Notepad++ or other feature rich editors are very much preferred over the Windows standard editor. Notepad++ can be loaded from the corporate app store.
TestCases are sequences of Requests in Postman. A Postman Request combines a Pre-request Script, an actual HTTP request and a Test Script. The Pre-request Script is for preparing the HTTP request. The Test Script is for assessing the response to the HTTP request. Both Pre-request and Test Script are little JavaScript programs, which are executed in the Postman JavaScript sandbox.
This sandbox relieves the ApplicationOwner from many, many tasks, which would have to be done in "real" JavaScript programming. Reading about
- language core (e.g. variables, datatypes, operations, conditions, loops, functions, error handling)
- composed datatypes and references should suffice for preparing.
It is necessary to read the chapter Writing Scripts at the Postman learning center to understand the specifics of the sandbox and particularly the handling of variables between the scripts.
Further on, it is recommended to new ApplicationOwners to study existing testcase collections for getting familiar with the basic structures.
In the ApplicationLayer , all Microservices are implemented as REST servers that exposes APIs. Node.js is one of the perfect approaches to implement REST APIs. All ApplicationImplmenters require to install Node.js and npm in their local development environment. Both Node.js and npm are available for Linux, Windows and Mac.
Concepts
- Introduction to Node.js
- Introduction to npm
- Implementing Node.js application in VSCode
- Running Node.js Applications in VSCode
- Debugging Node.js Applications in VSCode
Step-by-Step Guidelines
- Implementing Node.js application in VSCode
- Running Node.js application in VSCode
- Debugging Node.js application in VSCode
Documentation
Please make sure that you are installing Node.js version >= 14 and npm version >=6.14.13
Writing a code that is mode declarative, communicates better and makes it easy to read and understand by other team members. Also , one of the key aspects of Microservice is high maintainability. This means that , after releasing the first version of the sofware, Corrective, preventive, perfective, and adaptive software maintenance can be done at a low cost. This can be achieved by doing a clean code from the starting.
Concepts
Consistently using the same style throughout your code makes it easier to read. Code that is easy to read is easier to understand by you as well as by potential collaborators. Therefore, adhering to a coding style reduces the risk of mistakes and makes it easier to work together on software.
Step-by-Step Guidelines
<- Back to Introduction - - - Up to Main - - - Ahead to Specifying ->