Production app right now? Define the Enterprise Architecture: All classes that are imported via OpenAPI/Swagger will be used as a foundation for your Information Model in your Enterprise Architecture. All you need to do is to define the relationships, keys etc to have one common ruleset for your organization. Keeps track of GDPR & CCPA data: Mark the properties of each class that contains personal data to easilly keep track of them when you build your dynamic workflow processes in Copyl. Can we use Copyl Integration Platform stand-alone? Yes you can. You do not need to use any other modules of Copyl to create integrations between your different systems.

Copyl is different from other Software-as-a-Service. We make a positive difference for thousands of businesses around the world. Our mission: Reinventing Productivity! We are working hard every day to develop smarter and better tools for all kinds of businesses around the world. If we make you more efficient at work, your company will be more sustainable, which is good for the community. When you feel you are in control you will get more energy and time for more innovative tasks. Find more info at https://www.copyl.com/en/software/contract-management. Copyl saves you a lot of time, money and energy. You will feel more ease and earn more money when you don’t have to keep track of all commitments and deadlines.

What is Contract Lifecycle Management? Contract Lifecycle Management (CLM) automates the process from contract initiation to contract signing and renewal/termination. You get a better visibility of your spending and revenue sources, as well as greater efficiency in your contract process. That results in lower costs for administration and mitigates the risk of paying suppliers that is terminated. Copyl has a free version of the Contract Management system (see below) that you can start using to keep track of your contracts and other documents.

When are microservices a bad design choice? If you are building a small application, or just building a prototype, it’s much easier to build a monolithic application. If the application doesn’t need to scale to multiple server instances it’s ok with a monolith. A middleway is to build a loosly coupled monolith that communicates internally via SOAP. You can also use some kind of user authentication that will send the user data in each call to the api. This is usually done by JWT (Javascript Web Token). We also recommend you to use Azure Active Directory (AAD) B2C tenant for your external users. We also recommend you to use an API Managment tool that will hide your api:s addresses, minimize requests, help you with versioning and also documentation. See more info at https://www.copyl.com/.

Don’t copy data between different microservices: Never change the data from another microservice directly. Instead use REST calls to the API of the other microservice. If other microservices are having an interest in the change of state – publish events to let all subscribers getting information about the change. You can either use a PubSub solution from your cloud vendor or use Copyl Integration Platform to report events and subscribe to them in other services.