# Wise Tech Stack (2022 edition)

DevFeed: [Wise Tech Stack (2022 edition)](<https://devfeed.tech/articles/wise-tech-stack-2022-edition-15458.md>)

Original publisher: [Read original article](<https://medium.com/wise-engineering/wise-tech-stack-2022-edition-a6ac089a382f?source=rss----f2565bbe9c46---4>)

Author: pavel dionisev

Published: 2022-12-07T08:04:11Z

Content type: article

Language: en

Sources: [Wise Engineering - Medium](<https://devfeed.tech/sources/wise-engineering-medium.md>)

Topics: [Back end](<https://devfeed.tech/topics/backend.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [Java](<https://devfeed.tech/topics/java.md>), [Spring Boot](<https://devfeed.tech/topics/spring-boot.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [API](<https://devfeed.tech/topics/api.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [java](<https://devfeed.tech/tags/java.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [platform](<https://devfeed.tech/tags/platform.md>), [spring-boot](<https://devfeed.tech/tags/spring-boot.md>), [tech](<https://devfeed.tech/tags/tech.md>), [tech-stack](<https://devfeed.tech/tags/tech-stack.md>)

## AI overview

Wise describes its 2022 technology stack, including microservices across backend, frontend, and mobile applications. Most backend services run on the JVM using Spring Boot and Java or Kotlin, while customer-facing applications use a framework built on Next.js.

## Source excerpt

Intro Two years passed since our last tech stack post. TransferWise became Wise and Wise became a public company. We've opened more offices in more locations and remote work was never as common. We faced more regulatory scrutiny, went through multiple audits, and proved to the world and our customers that we are trustworthy, and still laser focused on helping money move without borders. We kept going, kept opening new routes and launching new products, all in the new paradigm. Most importantly, we did it without slowing down, introducing extra complexity or bureaucracy to our processes. In this blog post we'll share how we achieved it. Photo by Sean Stratton on UnsplashProduct: Backend Microservices, Frontend, mobile and API Our product is at the core of what we do and it roughly consists of customer-facing frontend and mobile applications, and complex backend machinery that works under the hood to support our mission: money without borders -- instant, convenient, transparent and eventually free. It is not a small task. Luckily, we have more than 700 engineers forming approximately 100 teams that are very good at solving the problems that arise. Our stack follows that structure. We use microservices in backend, frontend and our mobile apps are also modularised to a small chunks owned by specific teams. Most of our over 600 backend services are running on JVM, use Spring Boot and written in Java or, sometimes, Kotlin. Early on we decided to encourage anyone to contribute to any service we have. To achieve that we needed to reduce the entry barrier, so common language as a foundation worked really well. Sticking to industry standard allows us to tap into a wide and diverse pool of engineers that can join us on our mission. Common, compatible runtime also enabled us to work on standardisation, and building tools and libraries that support each engineer: standardised observability, security, service-to-service communications and more. We abstracted a lot of underlying in