Hello everyone,
Containers, DevOps and microservices are quickly taking the world like fire. There won't be surprise if in 3-5 years microservice-based logic will become the mainstream approach to build complex systems. But there is one serious flaw in that approach. Microservices reject standards. There are so many different ways to build microservices that there is almost nothing to reuse. Market of ready-to-use microservices doesn't exist because it is not economically viable to cover so many platforms, communication and persistence technologies. To some degree that problem is mitigated by using external SaaS services. But as an owner, are you ready to give up control on a big chunk of your system? Or you would prefer to keep some components within your reach and under your control?
Pip.Services project is trying to close that gap. Using componentized architecture it delivers a library of reusable microservices that you can take and incorporate within your own system. If gives you more flexibility, more control and, perhaps, can seriously cut your operational costs. The flexibility of the Pip.Services architecture allows to plug virtually any storage, use any communication infrastructure and deploy or pretty much any platform.
We are happy to hear what do you think about this project. And will try our best to answer any questions and address any issues that will arise. Please, feel free to post your thoughts and your questions to Pip.Services discussion forum!
Pip.Services development team
