Cross-project integration



There was a need for consulting and architecture work over integration for several projects build in AWS environment. Projects were implemented using different programming languages, by different teams. They were developed and deployed on the production separately. But in overall they are connected with each in several ways:

  • Using the same shared services
  • Using the same data source (database, structured files)
  • Using the same infrastructure
  • Using the same security policy/roles

There were also new projects under implementation. Those new project or new requirements could change used and shared API’s, data structure or shift some changes in the infrastructure. If those changes will have any impact on the other projects it should be detected during the implementation by this platform.

Services performed

Software Applications


Digital Engagement

Web & Mobile Apps

Custom Application Development

Banking Platforms

Payment Methods


Deltek Maconomy

Adobe Magento

Key goals

Raise warning when new projects or changes will affect functionality of other project

Lower the number of errors during the implementation phase by automated tests

Lower the cost of development and tests with automated tests

Eliminate risk of errors caused by the new projects deployed to the production environment

Key features

Technologies used

  • AWS AMI (Amazon Machine Images),
  • AWS EC2 (Elastic Compute Cloud),
  • AWS S3 (Simple Storage Service),
  • AWS CloudFormation,
  • AWS Cloudwatch,
  • AWS CLI (Command Line Interface),
  • Jenkins Continuous Integration,
  • Sonarqube,
  • Maven,
  • Nexus,
  • HashiCorp Packer,
  • Bash scripting,
  • PowerShell,
  • Chef (Infrastructure Automation),RabbitMQ,
  • HA Cluster,
  • Angular,Python,
  • Java, NodeJS, Drupal, Unix,
  • Git, Bitbucket, SVN,
  • Slack – notification of an error for configured groups