[et_pb_section fb_built="1" admin_label="Challenge" _builder_version="3.22" collapsed="off"][et_pb_row column_structure="3_5,2_5" _builder_version="4.1"][et_pb_column type="3_5" module_class="ds-vertical-align" _builder_version="3.25" custom_padding="|||" custom_padding__hover="|||"][et_pb_text admin_label="Challenge" _builder_version="4.1"]


In this case study we shall examine the uses and advantages of Docker architecture and the benefits of a Kubernetes cluster.

One of our existing clients had been using their own machine learning strategies to develop an in-house platform in order to produce trading signals from a range of alternative datasets. The 4-person development team had been running for six months, working on building a suite of Python applications and Big Data processing pipelines, both on premise and in Amazon AWS cloud.

    [/et_pb_text][/et_pb_column][et_pb_column type="2_5" module_class="ds-vertical-align" _builder_version="3.25" custom_padding="|||" custom_padding__hover="|||"][et_pb_text _builder_version="4.1" background_color="#ffbb22" custom_padding="10px|10px|10px|10px|false|false"]


    • 4-person in-house development team
    • Alternative data sets
    • In-house VMware and AWS cloud
    • Proprietary Python and TensorFlow code
    • MongoDB for data and results
    [/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version="4.1"][et_pb_column type="4_4" _builder_version="4.1"][et_pb_text _builder_version="4.1"]

    The client approached Hentsū to extend their own small development team, and to improve the overall software development. The pace of functionality releases was slow, the applications were suffering from complexity and the code quality was poor.

    The in-house developers were experiencing significant struggles to work as a unified team. Code was being committed and deployed with broken library dependencies, resulting in manual fixes every release to ensure code was running correctly. The applications were disjointed and inconsistent, with very loosely coupled sets of scripts, software, and services. There was no robust deployment of the applications, and once deployed there was often the need to intervene manually.

    [/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section][et_pb_section fb_built="1" _builder_version="4.1" background_color="#333333"][et_pb_row _builder_version="4.1" width="90%"][et_pb_column type="4_4" _builder_version="4.1"][et_pb_text _builder_version="4.1" ol_font="|600|||||||" ol_text_color="#ffbb22" custom_padding="20px||||false|false"]

    document icon Key Requests

    1. Deliver more functionality, faster
    2. Reduce code bugs and improve stability of the application
    3. Deploy the application faster to any environment
    [/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section][et_pb_section fb_built="1" admin_label="Solution" _builder_version="4.1" collapsed="off"][et_pb_row column_structure="2_5,3_5" _builder_version="4.1" custom_margin="30px||||false|false" collapsed="off"][et_pb_column type="2_5" module_class="ds-vertical-align" _builder_version="3.25" custom_padding="|||" custom_padding__hover="|||"][et_pb_text _builder_version="4.1" background_color="#ffbb22" custom_padding="10px|10px|10px|10px|true|true"]

    Technologies Used

    • Atlassian JIRA – roadmap, sprints and issue tracking
    • Atlassian Confluence – documentation
    • Atlassian BitBucket – source code
    • Atlassian Pipelines – build, testing and deployment
    • Amazon AWS – Elastic Container Registry (ECR) and environments
    [/et_pb_text][/et_pb_column][et_pb_column type="3_5" module_class="ds-vertical-align" _builder_version="3.25" custom_padding="|||" custom_padding__hover="|||"][et_pb_text admin_label="Solution 1" _builder_version="4.1"]


    DevOps Workflow

    Hentsū promptly identified the need to deploy the most efficient Continuous Integration/Continuous Deployment (CI/CD) pipeline, as fast as possible. The focus had to be on feature development rather than tooling, as well as on the removal of any difficulties in getting great code from the developers - quickly.

    As a first phase, Hentsū deployed a development workflow, which was based around the Atlassian suite of products. The goal was to enable rapid iteration of the team’s code, whilst ensuring overall software testing, quality control and integration. The workflow relied on properly defined environments – Development, Testing, Acceptance, Production (DTAP).


    [/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version="4.1"][et_pb_column type="4_4" _builder_version="4.1"][et_pb_image src="https://hentsuprod.wpengine.com/wp-content/uploads/2018/06/DevOps-Workflow.jpg" show_in_lightbox="on" align_tablet="center" align_phone="" align_last_edited="on|desktop" admin_label="DevOps Workflow" _builder_version="3.23"][/et_pb_image][et_pb_text _builder_version="4.1"]

    Deploying these steps and enforcing the code flow produced an instant improvement in both the collaboration across the team, and the quality of software. There was much improved visibility on what any one developer was pushing into the branches and its effect on the overall software.

    Separately, Hentsū worked with the developers to restructure the Git software repositories logically into specific areas of concern (apps/services/dependencies). Each repository would contain its own tests, dependency tree and Bitbucket pipeline YAML config. This enabled more autonomy in development, whilst retaining efficient control over the cross-platform dependencies and testing.

    Finally, the agile methodology was improved through the use of clearer structure and scheduling. Ensuring better code quality and higher feature throughput was key. So, there was a focus on activities such as sprint start, standups, development time, smoke tests, and backlog refinement. Product ownership and feedback were improved within the business. This was accomplished by clearly identifying each feature owner and involving them in the sprint process.

    [/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section][et_pb_section fb_built="1" _builder_version="4.1" background_enable_color="off" collapsed="off"][et_pb_row _builder_version="4.1"][et_pb_column type="4_4" _builder_version="4.1"][et_pb_text _builder_version="4.1" hover_enabled="0" locked="off"]


    [/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row column_structure="3_5,2_5" _builder_version="4.1" width="100%" custom_margin="||0px||false|false" custom_padding="10px||0px||false|false" collapsed="off"][et_pb_column type="3_5" module_class="ds-vertical-align" _builder_version="3.25" custom_padding="|||" custom_padding__hover="|||"][et_pb_text admin_label="Solution 2" _builder_version="4.1"]

    Docker Architecture

    Hentsū deployed a 3-person team to augment the in-house developers. The team brought Python and containerisation expertise to re-architect the applications and make them more stable, self-contained, and easily distributed across environments. Whilst the Git repositories were restructured, the corresponding Docker images were rolled out for each specific service.

    Docker registry and Elasticsearch services from AWS were used to help with the deployments and monitoring, without having to stand up infrastructure. To help with the deployment, scaling and management of the Docker containers, a Hentsū customised Kubernetes platform was rolled out. The customisation also allowed the client to overcome the limitations in the AWS EKS service and integrate VMware environments. This ensured consistency of deployment and tooling, but also allowed for the applications to be deployed to Azure and Google Cloud Platform (GCP).

    If you wish to learn more about Docker, check out our blog posts:

    [/et_pb_text][/et_pb_column][et_pb_column type="2_5" module_class="ds-vertical-align" _builder_version="3.25" custom_padding="|||" custom_padding__hover="|||"][et_pb_text _builder_version="4.1" background_color="#ffbb22" custom_padding="10px|10px|10px|10px|false|false"]

    Technologies Used

    • Docker – containerisation
    • Angular – front end interfaces
    • Kubernetes – cluster management
    • Helm – package management
    • Kubespray and Ansible – Kubernetes deployment
    • AWS Elasticsearch, Prometheus and Grafana – application and system monitoring
    [/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row column_structure="1_2,1_2" _builder_version="4.1"][et_pb_column type="1_2" _builder_version="4.1"][et_pb_image src="https://hentsuprod.wpengine.com/wp-content/uploads/2018/06/Kubernetes-Cluster.png" show_in_lightbox="on" align_tablet="center" align_phone="" align_last_edited="on|desktop" admin_label="Kubernetes Cluster" _builder_version="3.23"][/et_pb_image][/et_pb_column][et_pb_column type="1_2" _builder_version="4.1"][et_pb_image src="https://hentsuprod.wpengine.com/wp-content/uploads/2018/06/Security-Kubernetes-Cluster.png" show_in_lightbox="on" align_tablet="center" align_phone="" align_last_edited="on|desktop" admin_label="Security Kubernetes" _builder_version="3.23"][/et_pb_image][/et_pb_column][/et_pb_row][et_pb_row _builder_version="4.1"][et_pb_column type="4_4" _builder_version="4.1"][et_pb_text _builder_version="4.1"]

    Kubernetes Cluster

    Using a Kubernetes cluster, Hentsū enabled the additional functionality of automatic scaling. Worker nodes were able to run as a static number, which could be useful on-premise to limit the impact on other resources. However, as the Python code had the capability to work in parallel, deploying autoscaling allowed the number of nodes to ramp up quickly based on the queue of work. If there was a bigger queue of incoming data to process, the entire cluster could autoscale to thousands of nodes if needed. Each individual worker node was a small enough unit of compute/memory that the autoscaling for different loads of work became very linear and cost efficient.

    Combining the Hentsū Kubernetes cluster management and AWS meant that the client had many more options to manage the workloads. The cluster could rapidly adapt between specific GPU enabled worker instances, whilst simultaneously the client was able to use the AWS Spot market for cheaper resources when available and move the application between regions or even cloud providers. Another new possibility this opened up was deploying to bare metal, allowing for VMware to be discarded.

    [/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section][et_pb_section fb_built="1" _builder_version="4.1" collapsed="on"][et_pb_row _builder_version="3.25" background_size="initial" background_position="top_left" background_repeat="repeat"][et_pb_column type="4_4" _builder_version="3.25" custom_padding="|||" custom_padding__hover="|||"][et_pb_text admin_label="Solutions 3" _builder_version="4.1"]

    Security Considerations

    With the ability to run the Python code in various cloud platforms, and potentially also utilise Platform as a Service (PaaS) from the cloud providers, the security of the intellectual property was of concern. Hentsū deployed the entire solution with strict adherence to its own developed ISO 27001 cloud security checklist. Encryption was built into the application from the start, and all user access controls were tied back to the client’s corporate Active Directory.

    [/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section][et_pb_section fb_built="1" admin_label="Impact" _builder_version="4.1" background_color="#333333" custom_margin="||30px||false|false" custom_padding="||||false|false" collapsed="on"][et_pb_row _builder_version="4.1" width="90%"][et_pb_column type="4_4" _builder_version="4.1"][et_pb_text admin_label="Impact" _builder_version="4.1" custom_padding="10px|10px|10px|10px|false|false"]


    The improvements and options Hentsū enabled meant developers were happier and substantially more productive with their coding. We've employed both Docker architecture and Kubernetes cluster successfully. Additionally, the team collaboration and the engagement of the business stakeholders meant that more features than initially planned were released to the end users, and in a faster timeframe.

    The number of bugs which were raised in production from each two-week release cycle was reduced from an average of over 30, to below 2. This code quality success was ensured by the improvements Hentsū implemented to the scheduling and structure, such as the Pipeline unit tests, the consistency of the development and acceptance environments, and the rigorous smoke tests.

    The greatest impact was the overall delivery of the project. When Hentsū was first engaged the estimate for remaining time to deliver the project was 18-24 months; however with the changes delivered by Hentsū the project was completed in under 6 months.

    [/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section][et_pb_section fb_built="1" admin_label="CTA" _builder_version="4.1" collapsed="off"][et_pb_row _builder_version="4.1"][et_pb_column type="4_4" _builder_version="4.1"][et_pb_cta title="Talk to us about your cloud workloads" button_url="https://hentsuprod.wpengine.com/contact" url_new_window="on" button_text="Contact Us Today" _builder_version="3.16" button_text_size__hover_enabled="off" button_one_text_size__hover_enabled="off" button_two_text_size__hover_enabled="off" button_text_color__hover_enabled="off" button_one_text_color__hover_enabled="off" button_two_text_color__hover_enabled="off" button_border_width__hover_enabled="off" button_one_border_width__hover_enabled="off" button_two_border_width__hover_enabled="off" button_border_color__hover_enabled="off" button_one_border_color__hover_enabled="off" button_two_border_color__hover_enabled="off" button_border_radius__hover_enabled="off" button_one_border_radius__hover_enabled="off" button_two_border_radius__hover_enabled="off" button_letter_spacing__hover_enabled="off" button_one_letter_spacing__hover_enabled="off" button_two_letter_spacing__hover_enabled="off" button_bg_color__hover_enabled="off" button_one_bg_color__hover_enabled="off" button_two_bg_color__hover_enabled="off"]See how Hentsū can enable your data science workloads across multiple clouds, using DevOps techniques and Docker containerisation. [/et_pb_cta][/et_pb_column][/et_pb_row][/et_pb_section]


    Date(s) - 01/01/1970
    12:00 AM - 12:00 AM


    600 5th ave. NY, NY