Task management app today? Find out the security requirements before building. Look at authentication, authorization, network topology, impersonization etc. What level of logging is needed? On success? On failure? How should these recepients be administred? For how long should the log be saved? common mistakes when developing integrations: One developer is assigned to develop the integration. Leaving non-updated code, dependency to the developer and to the tech used. Declaring a system to be not open for integration. There are a very few systems today that is totally closed and cannot be integrated. Big datasets are moved back and forth – only send the data that has changed.
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. Discover even more info at https://www.copyl.com/en/software/budget. Copyl helps you organize all your contracts. Get an overview over all contracts. Categorize them and group contracts by customer, supplier or framework agreement. You get an overview from where the revenue and costs comes from.
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.
One common way of describing the microservice’s methods is to use an OpenAPI/Swagger that will create an HTML-page with all methods and data models described. Swagger documentation will be created automatically if you use e.g. Swashbuckle in your .net project. Our free microservice template uses Swashbuckle to describe the microservice api. How to secure your microservices? There are multiple levels of security that you can implement on your microservices. First you should make sure that you have some kind of Web Application Firewall. That could be managed by your cloud provider (Azure, AWS, Google, Alibaba etc) or by a third-part like Cloudflare. This service will make sure that the requests that are coming in to your microservice is of good intentions. See more details 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.