Recently the first version of a system was put into production, which we helped to develop. This system is based on a microservice-architecture approach.
This approach has recently gained a lot of popularity. And as usual with ‘new things’, they are being hailed as being the best thing since sliced bread. However to realize the true ‘pluses and minuses’, you need to put building a system like this into practice. We did this, and we would like to tell about our experience.
On March 16, the new versions of php, namely v7.0.17 and v7.1.3, were released. This is good news for many php developers, but for us it has an extra meaning, because our patch has been accepted there. The patch that fixes ‘keep-alive’ connections in php-fpm sapi.
Php-fpm first appeared as a separate patch for php 5.2, adding a manager for fastcgi processes, that allows you to organize individual pools, monitors the execution times of workflows and much more. In the php 5.4 branch it was accepted as an official sapi, which mean we didn’t need to apply this patch every time a new bugfix version of php arrived.
In today’s article we are going to focus on the Angular2 framework . We will talk about the Angular1 drawbacks, describe the main changes in the new version of the framework and, most importantly, share our impressions of the new version of the software.
Our clients often try to push us to hire freelancers and remote developers to expand the team. Sometimes we agree, but more often – we actively resist the suggestion 🙂 This article will help us to understand various schemes of remote development and determine which schemes are efficient for different types of projects.
The first step is to define the terms. If we talk about physical location of employees and degree of their involvement in a project, there are two basic dichotomies: Contract vs Staff Employee and Office vs Remote Work.
Gramant © 2007—2019.
