Serverless

01

Overview

This case involves our collaboration with a key Enterprise client specializing in Big Data and data analytics.

The company's goal was to craft a Chrome extension with nearly identical functionality to the product's web version.

Illustration

Before developing the Chrome extension, there were a few concerns:

  • 01

    Uncertainty about the extension's demand among users.

  • 02

    The urgency to create the extension promptly.

  • 03

    Balancing the speed of development with maintaining high-quality standards.

The primary focus was on effectively handling backend operations, particularly concerning authorization specifics and technical challenges in synchronizing the web version and the extension.

To address these concerns, Quema specialists collaborated with the team, suggesting and discussing various solutions. Together, an approach that best suited the needs was selected.

Opting for the Agile methodology, we planned sprints and commenced our work for the team's convenience.

Within the scope of our partnership, we are actively engaged in a novel sub-project focused onthe development of a Chrome browser extension.

01

Overview

This case involves our collaboration with a key Enterprise client specializing in Big Data and data analytics.

The company's goal was to craft a Chrome extension with nearly identical functionality to the product's web version.

Illustration

Before developing the Chrome extension, there were a few concerns:

  • 01

    Uncertainty about the extension's demand among users.

  • 02

    The urgency to create the extension promptly.

  • 03

    Balancing the speed of development with maintaining high-quality standards.

The primary focus was on effectively handling backend operations, particularly concerning authorization specifics and technical challenges in synchronizing the web version and the extension.

To address these concerns, Quema specialists collaborated with the team, suggesting and discussing various solutions. Together, an approach that best suited the needs was selected.

Opting for the Agile methodology, we planned sprints and commenced our work for the team's convenience.

Within the scope of our partnership, we are actively engaged in a novel sub-project focused on the development of a Chrome browser extension.

01

Overview

This case involves our collaboration with a key Enterprise client specializing in Big Data and data analytics.

The company's goal was to craft a Chrome extension with nearly identical functionality to the product's web version.

Illustration

Before developing the Chrome extension, there were a few concerns:

  • 01

    Uncertainty about the extension's demand among users.

  • 02

    The urgency to create the extension promptly.

  • 03

    Balancing the speed of development with maintaining high-quality standards.

The primary focus was on effectively handling backend operations, particularly concerning authorization specifics and technical challenges in synchronizing the web version and the extension.

To address these concerns, Quema specialists collaborated with the team, suggesting and discussing various solutions. Together, an approach that best suited the needs was selected.

Opting for the Agile methodology, we planned sprints and commenced our work for the team's convenience.

Within the scope of our partnership, we are actively engaged in a novel sub-project focused on the development of a Chrome browser extension.

02

Description

In collaboration with the Frontend development team, we engaged in thorough discussions to outline our strategic next steps.

Our dialogue comprehensively covered all pertinent details and nuances, resulting in the formulation of the following key objectives: Frontend Development (FE)

Our focus in the FE domain revolves around crafting a Chrome browser extension based on Node.js. The planned steps include:

01.

Chrome Web Store Publication

Streamlining the process to publish the extension on the Chrome Web Store.

02.

SonarQube Integration

Seamless integration of the extension with the SonarQube system to enhance code quality.

03.

End-to-End Testing in CI/CD

Implementation of comprehensive end-to-end tests within the Continuous Integration/Continuous Deployment (CI/CD) pipeline.

04.

App Versioning Implementation

Establishing a robust system for app versioning to effectively manage versions and track changes.

05.

CI/CD Automation

Implementing CI/CD to automate and expedite the release of new versions, enhancing efficiency.

The pivotal challenge lies in architecting the backend infrastructure, as this component will integrate into the main platform and services, bearing the brunt of the overall system load. Addressing this challenge is crucial for the seamless integration and optimal performance of the entire system.

02

Description

In collaboration with the Frontend development team, we engaged in thorough discussions to outline our strategic next steps.

Our dialogue comprehensively covered all pertinent details and nuances, resulting in the formulation of the following key objectives: Frontend Development (FE)

Our focus in the FE domain revolves around crafting a Chrome browser extension based on Node.js. The planned steps include:

01.

Chrome Web Store Publication

Streamlining the process to publish the extension on the Chrome Web Store.

02.

SonarQube Integration

Seamless integration of the extension with the SonarQube system to enhance code quality.

03.

End-to-End Testing in CI/CD

Implementation of comprehensive end-to-end tests within the Continuous Integration/Continuous Deployment (CI/CD) pipeline.

04.

App Versioning Implementation

Establishing a robust system for app versioning to effectively manage versions and track changes.

05.

CI/CD Automation

Implementing CI/CD to automate and expedite the release of new versions, enhancing efficiency.

The pivotal challenge lies in architecting the backend infrastructure, as this component will integrate into the main platform and services, bearing the brunt of the overall system load. Addressing this challenge is crucial for the seamless integration and optimal performance of the entire system.

02

Description

In collaboration with the Frontend development team, we engaged in thorough discussions to outline our strategic next steps.

Our dialogue comprehensively covered all pertinent details and nuances, resulting in the formulation of the following key objectives: Frontend Development (FE)

Our focus in the FE domain revolves around crafting a Chrome browser extension based on Node.js. The planned steps include:

01.

Chrome Web Store Publication

Streamlining the process to publish the extension on the Chrome Web Store.

02.

SonarQube Integration

Seamless integration of the extension with the SonarQube system to enhance code quality.

03.

End-to-End Testing in CI/CD

Implementation of comprehensive end-to-end tests within the Continuous Integration/Continuous Deployment (CI/CD) pipeline.

04.

App Versioning Implementation

Establishing a robust system for app versioning to effectively manage versions and track changes.

05.

CI/CD Automation

Implementing CI/CD to automate and expedite the release of new versions, enhancing efficiency.

The pivotal challenge lies in architecting the backend infrastructure, as this component will integrate into the main platform and services, bearing the brunt of the overall system load. Addressing this challenge is crucial for the seamless integration and optimal performance of the entire system.

03

Requirements

Our design development must align with the following requirements:

icon

Cost Efficiency

Minimize initial costs while ensuring the effectiveness of the solution.

icon

Automatic Scaling Capabilities

Enable seamless automatic scaling to accommodate increased traffic demands.

icon

Reliability

Ensure the reliability and stability of the chosen solution.

icon

Multi-Environments Support

Incorporate built-in support for multiple environments, such as development, staging, and production stages.

icon

Flexibility for Architectural Changes

Provide flexibility for implementing changes in the architecture, allowing for adaptability and evolution as needed.

icon

Cost Efficiency

Minimize initial costs while ensuring the effectiveness of the solution.

icon

Automatic Scaling Capabilities

Enable seamless automatic scaling to accommodate increased traffic demands.

icon

Reliability

Ensure the reliability and stability of the chosen solution.

icon

Multi-Environments Support

Incorporate built-in support for multiple environments, such as development, staging, and production stages.

icon

Flexibility for Architectural Changes

Provide flexibility for implementing changes in the architecture, allowing for adaptability and evolution as needed.

03

Requirements

Our design development must align with the following requirements:

icon

Cost Efficiency

Minimize initial costs while ensuring the effectiveness of the solution.

icon

Automatic Scaling Capabilities

Enable seamless automatic scaling to accommodate increased traffic demands.

icon

Reliability

Ensure the reliability and stability of the chosen solution.

icon

Multi-Environments Support

Incorporate built-in support for multiple environments, such as development, staging, and production stages.

icon

Flexibility for Architectural Changes

Provide flexibility for implementing changes in the architecture, allowing for adaptability and evolution as needed.

04

Technologies

By mutual agreement, our project embraced a Serverless approach centered around API Gateway and AWS Lambda. The backend technology stack comprised the following key components:

/ 01 /

AWS API Gateway:
Functioning as our API interface, providing seamless connectivity.

/ 02 /

AWS Lambda:
Serving as the backbone of our serverless architecture, where our backend code seamlesslyexecutes.

/ 03 /

AWS Secret Manager:Safeguarding sensitive data, ensuring the security of our backend operations.

This three-component backbone allowed us to construct the backend infrastructure, granting access to our Lambdas from the main platform.

04

Technologies

By mutual agreement, our project embraced a Serverless approach centered around API Gateway and AWS Lambda. The backend technology stack comprised the following key components:

/ 01 /

AWS API Gateway:
Functioning as our API interface, providing seamless connectivity.

/ 02 /

AWS Lambda:
Serving as the backbone of our serverless architecture, where our backend code seamlesslyexecutes.

/ 03 /

AWS Secret Manager:Safeguarding sensitive data, ensuring the security of our backend operations.

This three-component backbone allowed us to construct the backend infrastructure, granting access to our Lambdas from the main platform.

05

Results

During the initial two months, the usage cost remained within the budget of up to $30.
As the user base and requests grew, a proportional increase in costs was observed.
The backend was strategically designed to meet specific requirements, including:

    Integration with SonarQube System:Enabling seamless integration of the extension with the SonarQube system for enhanced code quality.

    AWS Secret Manager:Centralised secure storage for keeping secrets and managing credentials our all variables per environment. We also rotate secrets on a schedule for security reasons.

    End-to-End Tests in CI/CD:
    Implementation of comprehensive end-to-end tests within the CI/CD pipeline, ensuring robust and reliable releases.

    App Versioning Implementation:
    Establishing a systematic approach for app versioning to manage versions and track changes effectively.

    CI/CD Automation:Implementing CI/CD to automate and expedite new releases, enhancing efficiency and responsiveness to evolving project needs.

05

Results

During the initial two months, the usage cost remained within the budget of up to $30.
As the user base and requests grew, a proportional increase in costs was observed.
The backend was strategically designed to meet specific requirements, including:

    Integration with SonarQube System:Enabling seamless integration of the extension with the SonarQube system for enhanced code quality

    AWS Secret Manager:Centralised secure storage for keeping secrets and managing credentials our all variables per environment. We also rotate secrets on a schedule for security reasons.

    End-to-End Tests in CI/CD:
    Implementation of comprehensive end-to-end tests within the CI/CD pipeline, ensuring robust and reliable releases.

    App Versioning Implementation:Establishing a systematic approach for app versioning to manage versions and track changes effectively.

    CI/CD Automation:Implementing CI/CD to automate and expedite new releases, enhancing efficiency and responsiveness to evolving project needs.

05

Results

During the initial two months, the usage cost remained within the budget of up to $30.
As the user base and requests grew, a proportional increase in costs was observed.
The backend was strategically designed to meet specific requirements, including:

    Integration with SonarQube System:Enabling seamless integration of the extension with the SonarQube system for enhanced code quality

    AWS Secret Manager:Centralised secure storage for keeping secrets and managing credentials our all variables per environment. We also rotate secrets on a schedule for security reasons.

    End-to-End Tests in CI/CD:
    Implementation of comprehensive end-to-end tests within the CI/CD pipeline, ensuring robust and reliable releases.

    App Versioning Implementation:Establishing a systematic approach for app versioning to manage versions and track changes effectively.

    CI/CD Automation:Implementing CI/CD to automate and expedite new releases, enhancing efficiency and responsiveness to evolving project needs.

06

Business value of collaboration with Quema

01.

Collaborative Synergy

Quema champions seamless collaboration with customer teams, cultivating an environment free from disputes or conflicts. Our commitment is to foster innovation without hesitation, allowing your existing team to engage effortlessly.

02.

End-to-End Excellence

At Quema, we pride ourselves on building solutions from the ground up and fearlessly undertaking turnkey projects or sub-projects. Our dedication to seeing projects through to completion ensures a comprehensive and impactful delivery.

03.

Strategic Precision

Embracing Agile and Scrum methodologies, Quema values structured planning and systematic execution. Our approach ensures a well-defined strategy, moving forward with precision and purpose rather than chaotically.

06

Business value of collaboration with Quema

01.

Collaborative Synergy

Quema champions seamless collaboration with customer teams, cultivating an environment free from disputes or conflicts. Our commitment is to foster innovation without hesitation, allowing your existing team to engage effortlessly.

02.

End-to-End Excellence

At Quema, we pride ourselves on building solutions from the ground up and fearlessly undertaking turnkey projects or sub-projects. Our dedication to seeing projects through to completion ensures a comprehensive and impactful delivery.

03.

Strategic Precision

Embracing Agile and Scrum methodologies, Quema values structured planning and systematic execution. Our approach ensures a well-defined strategy, moving forward with precision and purpose rather than chaotically.