Streaming with Kinesis
AWS Kinesis behind a resilient, auto-scaling platform that handles traffic spikes.
Cloud
AWS development services for traffic you cannot predict
Kinesis streams, microservices and managed data behind .NET and Node.js back ends. We have shipped three published builds on AWS, one designed for 30,000+ concurrent users with the first phase live in a month.
3Published builds on AWS
30,000+Concurrent users the crypto platform was built for
1 monthFirst phase delivery on that build
6Pillars in the AWS Well-Architected Framework
What we build
What we build on AWS
Auto-scaling microservices
Services split so each part scales on its own.
Hosted analytics platforms
A national education platform on AWS with Power BI on top.
Dedicated teams on AWS
Node.js, .NET and React teams that grew past 60 developers on AWS.
Architecture
Where AWS sits in a build
An AWS build for a gaming platform
Users
Angular web appFront end
Mini-games and adsEarn by playing and watching
Services
.NET microservicesScalable architecture
Streaming
AWS KinesisResilient, auto-scaling
Delivery
Daily CI/CDKanban workflow
From the cryptocurrency marketing platform for a Hong Kong business.
Review
Six questions to ask of any AWS workload
The AWS Well-Architected pillars
Operational excellenceRun and monitor systems, improve the process.
SecurityProtect data and systems.
ReliabilityRecover from failure and meet demand.
Performance efficiencyUse resources well as demand changes.
Cost optimizationAvoid spend that buys nothing.
SustainabilityReduce the environmental impact of the workload.
Source: AWS Well-Architected Framework. Sustainability was added as the sixth pillar in 2021.
Builds
The three builds
Fintech, Hong Kong
Cryptocurrency marketing platform
Microservices and AWS Kinesis built for 30,000+ concurrent users, with the first phase live in one month.
30,000+Concurrent users the platform had to support
Education, Norway
National education analytics platform
A .NET and Angular platform hosted on AWS, with Power BI insight for teachers and administrators.
No lossData moved from OPAL 1.0 to OPAL 2.0
Dedicated team, Germany
Core development team
Node.js, .NET, React and React Native on AWS, built by a team that grew to more than 60 developers.
60+Developers the team grew to
Fit check
When AWS is the right call
Pick AWS when
- Traffic arrives in spikes and the architecture must absorb them
- Your team and data already sit on AWS
- You want streaming or event-driven services
Look elsewhere when
- Your team already runs Microsoft 365, .NET and SQL Server on Azure
- The product is a small site with steady traffic
- You want to avoid committing to a single cloud
Related: Azure, .NET, Node.js, and the education and games sectors.
Stack
What AWS usually ships with
.NET
Node.jsAngular
React
Docker
KubernetesFAQs
What buyers ask first
Can you build for 30,000 concurrent users?
We built a platform for 30,000+ concurrent users on microservices and AWS Kinesis, with the first phase live in one month. Load depends on the design, so we test against your own target.
Should we pick AWS or Azure?
The choice follows where your team, data and licences already are. We have shipped three published builds on AWS and three on Azure.
What is the Well-Architected Framework?
AWS describes six pillars: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability. It is a useful checklist for reviewing any workload.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us what your traffic looks like
Thirty minutes on your load, your accounts and your current architecture. No sales pitch.