Serverless infrastructure

Industry

Retail & Logistics

Team setup

2 developers

Timeline

6 months (ongoing)

Problem to solve

Just like most of the ecommerce infrastructures, rieker-eshop.hu has 3 types of load: the business-as-usual (BAU) load (90% of the time), the increased load during sales periods (9% of the time), and the peak time load (1% of the time). The peak time load is around 50x higher than the business-as-usual. We needed an infrastructure that handles both types of load.

Challenge

We had limited resources (time-to-market, money, ops time, etc), and we wanted to build something that is secure, easy to change, operate, monitor and scale. All this without having a dedicated ops team.

Outcome

We decided to go with a serverless-first approach, so we could offload most of the operational tasks to the cloud provider (AWS in our case). We architected our system with serverless components like Lambda, DynamoDB, S3 or Api Gateway. As a result, we could focus on the business / customer needs, and our (DevOps) developers can deliver end-to-end features.

Serverless infrastructure

Industry

Retail & Logistics

Team setup

2 developers

Timeline

6 months (ongoing)

Problem to solve

Just like most of the ecommerce infrastructures, rieker-eshop.hu has 3 types of load: the business-as-usual (BAU) load (90% of the time), the increased load during sales periods (9% of the time), and the peak time load (1% of the time). The peak time load is around 50x higher than the business-as-usual. We needed an infrastructure that handles both types of load.

Challenge

We had limited resources (time-to-market, money, ops time, etc), and we wanted to build something that is secure, easy to change, operate, monitor and scale. All this without having a dedicated ops team.

Outcome

We decided to go with a serverless-first approach, so we could offload most of the operational tasks to the cloud provider (AWS in our case). We architected our system with serverless components like Lambda, DynamoDB, S3 or Api Gateway. As a result, we could focus on the business / customer needs, and our (DevOps) developers can deliver end-to-end features.

Serverless infrastructure

Industry

Retail & Logistics

Team setup

2 developers

Timeline

6 months (ongoing)

Problem to solve

Just like most of the ecommerce infrastructures, rieker-eshop.hu has 3 types of load: the business-as-usual (BAU) load (90% of the time), the increased load during sales periods (9% of the time), and the peak time load (1% of the time). The peak time load is around 50x higher than the business-as-usual. We needed an infrastructure that handles both types of load.

Challenge

We had limited resources (time-to-market, money, ops time, etc), and we wanted to build something that is secure, easy to change, operate, monitor and scale. All this without having a dedicated ops team.

Outcome

We decided to go with a serverless-first approach, so we could offload most of the operational tasks to the cloud provider (AWS in our case). We architected our system with serverless components like Lambda, DynamoDB, S3 or Api Gateway. As a result, we could focus on the business / customer needs, and our (DevOps) developers can deliver end-to-end features.

Serverless infrastructure

Industry

Retail & Logistics

Team setup

2 developers

Timeline

6 months (ongoing)

Problem to solve

Just like most of the ecommerce infrastructures, rieker-eshop.hu has 3 types of load: the business-as-usual (BAU) load (90% of the time), the increased load during sales periods (9% of the time), and the peak time load (1% of the time). The peak time load is around 50x higher than the business-as-usual. We needed an infrastructure that handles both types of load.

Challenge

We had limited resources (time-to-market, money, ops time, etc), and we wanted to build something that is secure, easy to change, operate, monitor and scale. All this without having a dedicated ops team.

Outcome

We decided to go with a serverless-first approach, so we could offload most of the operational tasks to the cloud provider (AWS in our case). We architected our system with serverless components like Lambda, DynamoDB, S3 or Api Gateway. As a result, we could focus on the business / customer needs, and our (DevOps) developers can deliver end-to-end features.

Browse more of our successes

Find more of our successes and learn about our processes!

Browse more of our successes

Find more of our successes and learn about our processes!

Browse more of our successes

Find more of our successes and learn about our processes!

Browse more of our successes

Find more of our successes and learn about our processes!

KCM tech.

© 2024 KCM tech. All rights reserved.

KCM tech.

© 2024 KCM tech. All rights reserved.