Contract management app right now? What is a monolith? A monolith is a common legacy software design were all logic is compiled together in one big chuck of software. The upcoming architecture is called microservices which are small, autonomous, software pieces. There are advantages of both of them. Can we replace the monolith with microservices? Yes. We usually recommend small steps and a bit of preparation to identify any potential obstacles. You should also be prepared to make organizational changes.
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 information on microservice management app. Collaborate with your colleagues. Copyl Contract Management solution enables you to share contracts and set permissions on them to allow certain groups/users access.
Access your Contracts from anywhere: There is no need to install any app and you can access all contracts and features via your mobile phone or tablet. Connect documents to your Contracts. Connect documents your Google Drive or upload directly to Copyl. Both signed documents and appendix etc can be connected. Electronic Signatures shortens process: Have your counterparts sign the contract and documents via an Contract Signature Request sent directly from Copyl user interface. The Contract is locked upon the first signature and everyone can access the contract afterwards.
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. Read even more info at copyl.com.
Copyl communicates with the user in all the steps of an transaction in your Saga. You configure the status in the API and Copyl transports it to the user. Each step in the Saga transaction has a compensating action that starts upon error in the transaction. When designing the API and the Saga structure there are some things to consider. The Saga will do each request anonymously. You can add headers to the request but cannot run as a user request with jwt. The Saga will have inparameters and then keep track of all data that are returned from each request in the transaction. This data can be used for other requests in the same transaction. You need to plan for all the data that is needed in the requests and their compensating actions when you design the api.