Boardroom & voting platform today? Autogenerate your App’s Actions! It is really super-easy to generate all available Actions in your API/App by pointing out the OpenAPI/Swagger file. Copyl Integration Platform parses this file and adds all available Actions together with information about fields needed. Even the documentation is available in CIP afterwards. You need to manually start the parser from the administration interface of your app. You can delete any unwanted Actions afterwards and you can also hide them when generating the Swagger file.
Copyl is built in Sweden. Buying a whole ERP-system is so 2000. Today, all kinds of businesses are trying out new digital tools and implement them if they give a value. Many software-as-a-service (SaaS) are implemented by people outside the it-department. Things in common; easy to onboard, they are cheap and have good ux. During the covid-outbreak we totally redesigned Copyl. We spent a year building common building blocks that we can put different labels on, in different apps. Eg Task Management that you can connect as simple todo lists on Contracts in the Contract Management app or use in your Customer Support or Project Planning. Same tech – different labels. Find even more information on https://www.copyl.com/en/blog/how-we-designed-the-boardroom-software. Collaborate with your colleagues. Copyl Contract Management solution enables you to share contracts and set permissions on them to allow certain groups/users access.
All Contracts in one place! See current and past contracts from the overview page. Group by supplier, customer or status. Discuss and follow up on tasks: All contracts have their own forum were you and the counterparts can discuss the contract. The Task Management system in Copyl is also automatically connected to each contract. Integrated with Search and other pages: The contracts appears on the related contacts, search, projects and other pages were the contract is connected.
Why microservices? Microservices architecture means new opportunities for most organizations. Faster development and faster time-to-market. Independent services that can be released/updated at any time. The team is responsible for the application roadmap and for developing and maintaing the microservice. The team also has the freedom to use any technology within each service. The biggest challenges with microservice architecture: We know from our own experience and from helping other companies that implementation of microservice architecture means new challenges that needs to be addressed for a successful implementation. Read additional info at https://www.copyl.com/.
No – one database server for all microservices is not correct! If you are used to monolith application it can be tempting to create one (1) database server to manage all the data in the solution. That is not the correct way of implementing microservice architecture. Each microservice should host it’s own data in a server that is bundled together with the services for the microservice. Store data where it belongs: If much of the data belongs in multiple microservices, the design is probably wrong.