< Back to Case study

AWS Project Type: Next-Gen Cloud (Rearchitect)

Project Type
Architecture, IoT, Kubernetes, and Application Development on the AWS Cloud

About the Client
This UK-based business enjoys breaking new ground in integrated home energy solutions. Over the past decade they developed more than 25 products and sold over 4 million energy monitoring systems across the UK and Europe. In moving towards a smart energy future, they made the tracking of its usage more visible and use that to drive the engagement and behavioural change needed to shape a greener more fuel efficient society.

Challenge
As they integrated with more European utilities and retail partners, they needed to make an architectural shift with a partner who could help them move from a legacy monolith into microservices, and fully embrace the AWS Cloud Services offering. They attracted over 100K new users per month and needed to offer seamless coverage. They also required assistance migrating their on-premise solution to AWS and rerouting several million existing users onto these new services.

Solution
As part of the solution, microservices blueprints were designed for fast adoption and development; over 30 microservices were created to replace the monolith. CloudFormation was used for GitOps and Jenkins for Continuous Integration (CI) and Continuous Delivery (CD).

Additionally, AWS Elastic Beanstalk and Lambda were implemented for microservices orchestration and Dynamo and Kinesis were used to handle the massive loads for IoT.

Future executions mean we are currently working on energy specific POCs using EKS and Docker containers.

 AWS Services
CloudFormation, Beanstalk, RDS, API Gateway, Lambda, Kinesis, Dynamo DB, EC2, S3, SES, SNS, and SQS are used. For security we are making use of IAM and VPC. Security is increasingy a differentiator in Smart Home offerings.

Benefits
The solution helped the client reduce the cost of maintenance and monitoring, and improve the efficiency of continuous deployment. We also proved that high scalability was no longer an issues and fault tolerance was made more rigorous; Elastic Beanstalk was used in both these scenarios.