Product management platform today? 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 started out from our own needs. We had an agency with 30 consultants and we were planning them all in an Excel sheet. We love Excel but we quickly got different planning in the projects and in the resource planning. We needed something more connected. And something that we could follow up in the time sheets and billing process. After a few years with this planning system we got a call from a big organization in Sweden that needed a ERP system. We scanned the market for them, not able to find a perfect match. We had a meeting and we showed them we showed how we managed our own resource planning. Instantly the customer said that they wanted that system. Copyl 1.0 was born. This was 2011. Read extra information at resource planning. Get reminded before a contract reaches a deadline. We will send you an email before any important deadline on your contracts. Your colleagues will get the email if they are conntected to the contract.
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.
Copyl has a solution for the biggest challenges. How do microservices communicate with each other? The absolute most common communication between microservices are via REST API. It’s done over https and requires no or very little configuration on the network. We recommend to use the standard methods for your api requests; GET for fetching data, POST for saving new data, PUT for updating and DELETE for deletion. PATCH can also be used for updating, it’s a matter of taste. Read additional details on https://www.copyl.com/.
It’s a common issue that developers that are new to the design concept of microservices create too many service. A common design for a e-commerce solution is to have one microservice for Billing and another for Payment Collection. The Payment Collection microservice usually depends on Billing and Billing depends on knowing when a payment has been done. That’s a good reason to have both functionalities in one microservice.