Skip to content
Jetorbit
EN
Products
Login CloudLogin Client

Inkanteen

· Case study · Managed service

When Inkanteen moved from AWS to Jetorbit Cloud

Inkanteen was a technology startup serving small businesses, cafes, restaurants and school canteens: visitors ordered and paid by scanning a barcode in a pre-order system, and business owners received and prepared the orders from the Inkanteen app and website. Visitors did not have to queue to order.

note

Inkanteen has ceased operations and no longer subscribes to Jetorbit services. We keep the story of its migration as a picture of how the Jetorbit team carries out Managed Service work.

See Managed ServiceHow the migration went
Inkanteen logocase study › managed service
Status
No longer operating
Industry
Canteen ordering & payments
Users
Small businesses, cafes, restaurants, school canteens
Previously
AWS
Moved to
Jetorbit Cloud + Managed Service
Approach
1:1 matching
// 01 · challenges

Two things the Inkanteen team emphasized

Inkanteen saw heavy traffic at certain hours, so at the time it needed high availability and reliability precisely during those hours.

Lower costs

The Inkanteen team contacted Jetorbit looking for a cloud that cost less than what they were using at the time. After some discussion, Jetorbit drew up a cloud topology that matched their setup, complete with a cost breakdown.

Time

Until the migration was finished, the bill at the old provider kept running. The move therefore had to be quick, without disrupting the service Inkanteen’s customers were using.

// 02 · solution

1:1 matching with the AWS setup

Inkanteen wanted to keep the same technology it used on AWS: Kubernetes infrastructure, load balancing, CI/CD, down to a VPN for internal access. Jetorbit Cloud differs from AWS, so the Jetorbit team mirrored each service they used there as closely as possible.

  1. 01

    Assessment

    Listing the services running on AWS and the target topology.

  2. 02

    Trial run

    Several services were brought up on Jetorbit Cloud first for testing.

  3. 03

    Migration & data replication

    Services were moved in stages and their data replicated before the DNS change.

  4. 04

    Internal simulation

    The team made sure everything worked before user traffic was switched over.

  5. 05

    DNS change

    DNS was propagated to Jetorbit Cloud, then the data was reconciled.

// 03 · technology

The technology used

The same as on AWS, just in a new home. For as long as Inkanteen subscribed, everything ran on Jetorbit Cloud and was maintained by the Jetorbit team through Managed Service.

  • Kubernetes
  • Traefik
  • Jenkins
  • Redis
  • RabbitMQ
  • PostgreSQL

Want to migrate the same way?

Tell us about the setup you are running now. The Jetorbit team draws up the topology and the cost breakdown first, as it once did for Inkanteen.

Ask on WhatsAppManaged Service pricing