All success stories

From a single server to a production-ready e-commerce platform

CloudVests moved Block-O's construction-supplies platform off a single DigitalOcean server onto an auto-scaling, multi-AZ AWS architecture built for growth.

ClientBlock-O
0data loss at migration
0user interruption at cutover
15K+daily records automated
Removedsingle points of failure

Core services in the architecture.

A focused view of the AWS services most representative of this engagement. The complete technical scope is described below.

  1. 01AWS Application Migration Service
  2. 02AWS Database Migration Service
  3. 03Amazon RDS
  4. 04Amazon S3
  5. 05AWS Lambda
  6. 06Amazon CloudFront
  7. 07AWS WAF
  8. 08Amazon CloudWatch
01

The challenge

Block-O's construction-supplies platform ran on a single DigitalOcean server with no high availability, read replicas or automated backups, while high traffic and a supplier SaaS expansion were on the way.

02

What CloudVests delivered

CloudVests moved Block-O to a highly available, auto-scaling AWS architecture in Frankfurt, defined end to end in AWS CDK.

The ASP.NET application was containerised on Amazon ECS with AWS Fargate, and PostgreSQL moved to Amazon RDS in a Multi-AZ deployment with a read replica. Amazon ElastiCache, Amazon S3 and CloudFront handle caching and media delivery, with AWS WAF protecting the edge.

A GitHub-to-AWS CodePipeline workflow automates releases, and AWS Backup and CloudWatch cover backups and monitoring. Load, failover and restore tests, an ArchMate security assessment and a Well-Architected review were completed before cutover.

03

The outcome

Block-O now runs on a highly available platform instead of a single server, scaling with demand and failing over automatically.

The same foundation is ready for its next stage: a multi-tenant SaaS model for construction-material suppliers.