Independent consultancy / Toronto

Software development, security and architecture.

We help teams build applications, review security and make technical decisions about the systems they operate.

An order comes in. Then what?

An online shop has outgrown its first server. Send a burst of orders through the original system, then run the same load through our proposed architecture.

Cloud region · one availability zoneOne public virtual machineCustomersBrowsing & checkoutShop applicationCheckout & order APIOrders databaseOn the same machineFulfilment jobs0 queuedHTTPSOne CPU budget. One disk. One failure point.
Send ordersBlue: requests · Green: background jobs
Received0
Orders saved0
Fulfilled0
Rejected0
Model time0s
Choose a load to start. Switch architectures to replay it.
Everything shares one machine

This is a reasonable place to start. It becomes a problem when checkout slows during fulfilment runs, or a server failure stops both sales and order processing.

How this model works

This is an explanatory simulation, not a benchmark or a capacity promise. Orders arrive over ten model seconds; one model second takes 250 ms. Each moving light represents traffic, not a single request.

Before: a 100-request buffer, 20 orders saved per second, falling to 8 while jobs compete for the server; 5 fulfilments per second and a 100-job queue. After: durable intake sized for this one-million-order burst, consumers scaling from 1,000 to 20,000 orders per second, fulfilment scaling from 500 to 20,000 per second, and a 100,000-job queue. These capacities represent a provisioned target design; scaling time and throughput are model assumptions. Overflow is rejected and would need client retries. Actual sizing needs load testing.

The diagram shows the intended deployment; this simulation covers traffic and queue capacity, not zone failures or database failover. Scroll the diagram sideways on smaller screens.

Architecture services and estimates

Services

Engagements range from focused reviews to implementation work. These estimates give you a starting point for a conversation.

Software development

Applications, APIs, integrations and automation. Work can start with a defined feature, an existing codebase that needs attention, or an early product that needs technical direction.

CAD $3,000–$18,000Typical scoped engagement
Scope, timing and pricing

Cybersecurity

Technical security reviews, threat modelling and incident preparation for software teams. The focus is on your actual application, infrastructure and operating practices.

CAD $2,500–$10,000Typical scoped engagement
Scope, timing and pricing

Systems architecture

System design, platform reviews and migration planning grounded in how the software will be built and operated. Architecture work can include implementation where that is the best way to validate a decision.

CAD $3,000–$12,000Typical scoped engagement
Scope, timing and pricing

About Vimwire

Vimwire Ltd is an independent consultancy in Toronto, founded by Maxim Mirkin. We work across software development, cybersecurity, automation and systems architecture.

We can help with a defined implementation, investigate a problem in an existing system, or review a technical direction before your team commits to it. The scope and deliverables are agreed before the work starts.

Discuss a project

Send a brief description of the work, your current system and any relevant constraints. We can arrange a conversation to define the scope.

© 2026 Vimwire LtdSoftware development / Cybersecurity / Systems architecture