Skip to content
Case studies

Aquatic Informatics: repeatable delivery for mixed workloads

Containerization, AWS EKS and an automated CI/CD approach supported Aquatic Informatics’ transition toward a more mature multi-tenant environment.

  • Executive sponsors
  • IT managers
  • Project managers
  • Architects and engineering leaders
Conceptual architecture

The project context

Aquatic Informatics develops software that organizes water data. The engagement addressed a mixed technology environment as the application evolved from single-tenant assumptions toward multi-tenant delivery.

Compatibility and tenancy together

Windows and Linux workloads, application delivery and authentication needed to work as a coherent platform. Treating container deployment alone as the outcome would leave operational and user-access problems unresolved.

The architecture in context

Conceptual architecture

Conceptual architecture illustrating decision boundaries. It does not represent a client environment.

The implementation approach

  1. 01Prepare the application to run in an AWS EKS environment.
  2. 02Create an end-to-end build, test and deployment pipeline using Cloud Launchpad patterns.
  3. 03Integrate security operations and automated quality checks into delivery.
  4. 04Validate mixed operating-system workloads and Active Directory-related user authentication scenarios.

What made the work an architecture problem

The delivery path had to support different application technologies while improving tenancy, security and visibility. Platform choices were evaluated through application compatibility and the operating model, not in isolation.

Delivered direction

  • A more repeatable path to build, test and deploy application changes.
  • A platform design supporting the client’s multi-tenant evolution.
  • Security and quality checks connected to the delivery workflow.
  • Improved visibility into the application and its operating environment.

Lessons for another software team

Choose a representative application path early and test its operating-system, identity and tenancy assumptions. Automation is useful when it makes those dependencies visible and repeatable.

Frequently asked questions

Questions and answers

Why were mixed workloads important?

The source project describes both Windows and Linux containers. Their compatibility and authentication requirements had to be addressed in the platform and delivery design.

#
How did Launchpad relate to the project?

Cloud Launchpad supplied reusable delivery patterns for the CI/CD approach. The application and tenancy requirements still determined the project-specific implementation.

#
What can another software company reuse?

Dependency-led assessment, repeatable deployment and integrated validation are transferable practices. A new application requires its own security, tenancy and operating decisions.

#
A clearer starting point

Your next cloud decision starts here.

Tell us about your environment, priorities and next cloud decision.