25 10 21

Information models app 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.

All your data is stored in Europe (not UK). That eliminates the risk of having US governmental organizations looking at your data. Our team has been building complex web applications since the dawn of Internet. We know a lot about the latest tech, ai/ml, ux, scalability and security. And we know about business needs and challenges. When we started working on this latest version of Copyl we started from scratch. No code from earlier versions. We wanted to build an intelligent, modern, software that would fit both startups and big enterprises. With a business model that everyone would benefit from. See extra information on contract management. Collaborate with your colleagues. Copyl Contract Management solution enables you to share contracts and set permissions on them to allow certain groups/users access.

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. Discover additional details at https://www.copyl.com/.

Designing a monolith database is much different from designing multiple databases in a microservice architecture. As you know, we must have full independence on the different microservices and that also applies on their databases. A microservice is a design concept that bundles together all services needed to deliver the functionality specified. There are usually one team developing and maintaining each microservice, so communication between teams is important.