AI only works with architecture: watch the masterclass now 
Digital innovation in the building materials trade: AI image search for STARK Germany 
The right system for every application: Medienwerft Demo Days – See for yourself 
End2End solutions from UX to hosting: Benefit from the expertise of the FIS Group! 
Do you fit into our team? Discover all vacancies now and apply now! 
Ready for the shipyard? Find out what you can look forward to as an apprentice at Medienwerft! 
AI expertise in three episodes: Listen to our podcast series now! 
Composable commerce reimagined: Discover Emporix's new strategy now! 
Three use cases: Watch the AI Booster in Retail webinar now! 
Gateway to the HABA worlds: the Medienwerft LCS Middleware
The LCS (Lean Commerce Stack) middleware developed by us played a key role in replatforming the HABA Play and HABA Pro online shops. As a backend-for-frontend system (BFF), it forms the central link between the storefront and the backend systems in the HABA infrastructure.
What is so special about our middleware?
The middleware combines proven concepts from the JavaScript/TypeScript world with an architecture designed for extensibility. This includes:
- Express.js: A fast and minimalistic framework for server-side applications that offers high flexibility in development.
- TypeScript: Thanks to strict typing and good IDE support, TypeScript increases code quality and reduces potential sources of error.
- Modularisierung:The middleware is structured as a modular system – in this orchestration-first architecture, individual modules can be easily added or adapted, allowing even complex requirements to be mapped.
How does the middleware fit into the MACH architecture?
The MACH architecture is based on microservices, API-first, cloud-native and headless, and this is precisely where our middleware comes into its own:
- Microservices: Our middleware orchestrates various microservices that run independently of each other. For example, the content management service from “HABA Play” is also used for “HABA Pro”, while new B2B-specific services such as pricing logic have been seamlessly added.
- API-First: As a central API hub, the middleware ensures that all services communicate via defined interfaces. This ensures stable and flexible integration between the systems.
- Headless: The decoupled design ensures that the front end can be developed flexibly without having to make changes to the back end. This means that different frontends can be easily integrated for specific requirements.
Why Express.js and TypeScript?
- Future-proof: Thanks to its flexibility and strong community, Express.js remains a relevant and proven platform for middleware integrations. With its modern features and established best practices, TypeScript offers a robust basis for scalable and agile further developments.
- Performance: The minimalist approach of Express.js in combination with the efficient memory management of Node.js ensures high-performance and smooth requests. In addition, the technological proximity to web-native caching mechanisms and the simple integration of these technologies enable an optimal increase in performance.
- Ease of development: Thanks to TypeScript, developers can work more efficiently as potential errors are recognized and avoided at development time. This leads to a more stable code base and reduces maintenance costs in the long term.
- Modularity and reusability: Our tried-and-tested modules and implementation templates allow integrations between the application and the background systems to be implemented efficiently. This accelerates the rollout and increases the scalability of our solutions.
Conclusion:
Our middleware combines proven technologies with modern concepts and fits perfectly into the MACH architecture. It therefore offers an ideal basis for designing flexible and scalable online stores such as the B2B store “HABA Pro” – both today and in the future.
Any questions?
E-commerce middleware serves as an intermediary and translator between the backend and frontend of a system. Examples of this are address data and orders that are transferred from the frontend to the backend.
The aim is to use e-commerce middleware to link the frontend to the e-commerce backend so that other technologies, such as a CMS, can be easily connected in the future.
- LCS Middleware von Medienwerft:
Advantage: Headless architecture with clear API separation – ideal for modular stores
Disadvantage: No “out-of-the-box” solution – initial consulting and setup required - Spryker Middleware (GLUE API):
Advantage: Customized to your system landscape and e-commerce processes
Disadvantage: High complexity – requires developers with experience in API design - Tradebyte:
Advantage: Fast connection to marketplaces such as Zalando, OTTO or Amazon
Disadvantage: Strong focus on marketplaces – less flexible for individual systems - Intershop Commerce Hub:
Advantage: Deep integration of order management and PIM possible
Disadvantage: Limited to Intershop ecosystem – little openness to the outside - Synesty Studio:
Advantage: No/low-code automation, can also be used by non-developers
Disadvantage: Quickly confusing with very complex data models - Lobster data:
Advantage: Visual data integration with strong data protection (German provider)
Disadvantage: High license prices with increasing volume
Replatforming means transferring an existing system (e.g. an online store) to a new technical platform – without completely reinventing the entire business model or user guidance.
Typical for replatforming:
- new store software or cloud environment
- better performance, scalability or flexibility
- existing data and processes are migrated instead of replaced
Replatforming and middleware are closely linked – because middleware plays a central role when a system “moves” but should continue to communicate smoothly with other systems.
What is the connection?
Replatforming involves replacing a store system, CMS or ERP with a new one, for example. However, the surrounding systems – such as PIM, CRM, payment or logistics – often remain in place. This is exactly where middleware comes into play:
Why middleware is crucial for replatforming:
- Connecting systems
Middleware ensures that old and new systems can run in parallel – during the transition phase, for example. - Control data migration
It handles the structured transfer of product data, customer information or order histories. - Minimize risk
Thanks to middleware, interfaces can be adapted step by step instead of converting everything at once – this reduces downtime. - Ensure future-proofing
If you use middleware, systems are loosely coupled, which makes subsequent changes or extensions much easier.
