With the help of agile/scrum methodology we always stay focused on the most important things, therefore business critical features are on top and implemented first. We practice CI/CD, with automated pipelines, canary deployments, configuration management.

Product scoping

Architecture design

Software product development

Software testing

Software product support and maintenance

Users training

Professional consulting

Depending on exact project needs we develop optimal development schema and technologies to be involved.

EXAMPLE OF TECHNICAL APPROACH USED IN DEVELOPMENT

Architecture approach

Architecture should be designed and built according to Microservices Architecture (MSA) approach, to define and create systems through the use of small independent and self-contained services aligned closely with business activities.

For the interaction of components of a distributed system of applications we propose to use REST + Message Broker when DATA in topics are applicable and reusable for involved services with At-Most-Once delivery, At-Least-Once delivery or Exactly-Once delivery scheme.

For services architecture DataBase per service pattern is proposed as part of MSA when each microservice’s persistent data is kept private to that service and accessible only via its API. A service’s transactions only involve its DataBase.

Technology stack 

Proposal to use the following technologies:
Java, Spring Boot, Kubernates, Docker, RestAPI, Ceph, Streaming API
Apache Kafka, Sping Vault, Hashicorp Vault, PostgreSQL
MongoDB Spring Cloud Config,Redis
GitLab, SonarCube, Open VAS, ElasticSearch, Logstash, Kibana, Filebeat, Journalbeat. Haproxy, Nginx

Monitoring: Zabbix, Prometheus, Grafana. Logging: ELK, Sentry, Beats. Ability for tracing by request ID.

Information security approach

Strong cryptography with certification by the State Service of Special Communication and Information Protection. Production environment should has no Internet connection, all traffic (inbound and outbound) between different services has to be managed by Firewall.

All default passwords and accounts have to be changed.

All public faced libraries have to be up to date and periodically scanned by external and internal Vulnerabilities Scanning Software.

All passwords used by services and/or users have to be complaint to Passwords Policy and Procedures with rules like password rotations.

Deploy to Staging environment should be exposed by Unit tests, Integration tests, vulnerability tests.

Workflows approach

CI/CD: Git, GitLab, pipelines, Kubernetes, SonarCube, Sentry.

Change management, task management: Jira, Confluence, Slack, Jira Helpdesk.

Development: Agile, Scrum, SOLID, ACID.

Delivery: Deploy through several environments (Dev, Sandbox, Staging, Production), Blue/Green Deployments, Canary Deployments, Automatic Deployments after commit in isolated Dev environment.

Depending on project needs we practice the following:
The automated testing system is created to test new functionality, emulate artificial load and reproduce possible errors in a mode as close as possible to the real one. Deploy to Staging environment is exposed to Unit tests, Integration tests, Vulnerability tests. All modules of a software should be fully or partially covered with autotests and unit tests.

• Unit tests
• Integration tests
• Vulnerability tests
• Auto tests
• Manual tests