Moving from Java Spring framework to a ReactJS+APIs architecture

We’ve seen it a million times. Old platforms, created by dozens of developers over the course of as many years, with legacy code going back generations. The software works — but barely. And it’s badly in need of an overhaul.

But here’s the catch: how can a business start a digital transformation on a mission-critical platform without disrupting operations?

We’ve worked on cases like this several times, transforming Java platforms (also .Net, Rails, you name it) to modern architecture. And trust me: it is possible. Check this link with a lot of high profile case studies. This is a more down to earth article, with a more concrete example, after the one I wrote some time ago. It can be a good reference though.

Why change platform architecture?

• You can’t publish an update without introducing lag, risks, and even messier code.
• You want to move faster, have a good looking site, and improve your UX, but you don’t know where to start.
• You have to upgrade your stack and embrace newer technologies or face becoming obsolete.

Current architecture

Before we start to change platform architecture, we have to understand the current state…