How We Built Our Cloud‑Native Blog Using CAP, Fiori, and Next.js

 

At AppSkilling, we’re always exploring practical ways to blend SAP technologies with modern web development. Our own blog became the perfect opportunity to demonstrate one of our preferred approaches: a cloud‑native architecture powered by SAP CAP, SAP Fiori, and Next.js — all deployed seamlessly on a third-party Cloud Platform (Railway)

This isn’t a theoretical showcase. It’s the actual architecture behind the AppSkilling blog, built to be fast, maintainable, and adaptable as our content and platform evolve.

 

Note: This article is not sponsored by Railway. 

Why We Built It This Way

We wanted a setup that:

• delivers a fast, SEO‑friendly public website
• provides a clean, efficient admin interface
• uses CAP as a unified backend that can evolve with us
• deploys easily on a cloud platform without heavy infrastructure
• reflects the kind of cloud‑native SAP‑aligned solutions we build for clients

The result is a lightweight, modern architecture that demonstrates how SAP technologies can fit naturally into today’s cloud‑native development patterns.

The Architecture Behind the AppSkilling Blog

Next.js — The Public Website

The blog’s frontend is built with Next.js, giving us:

• fast rendering
• excellent SEO
• smooth routing
• a modern, responsive UI

It consumes data directly from CAP, keeping the frontend simple and efficient.

SAP Fiori — The Admin Dashboard

Instead of building a custom CMS from scratch, we used SAP Fiori Elements to create a personal dashboard for managing:

• posts
• views and reacts
• draft-enabled posts
• future analytics

Fiori’s metadata‑driven approach allowed us to build the admin interface quickly while maintaining a clean, enterprise‑grade UX.

SAP CAP — The Cloud‑Native Backend

CAP serves as the backbone of the entire system. It provides:

• a unified data model
• OData services for both Fiori and Next.js
• built‑in validations and logic
• clean extensibility for future features
• handles authentication for the dashboard and securely protects API from CORS attack

This is where the architecture becomes cloud‑native: CAP doesn’t care what frontend consumes it. It simply exposes clean, consistent services that can scale and evolve independently.

Railway — Simple, Cloud‑Native Deployment

Railway hosts all components with:

• straightforward service deployment
• internal networking
• built‑in database provisioning (Managed PostgreSQL)
• environment variable management
• git-enabled automatic deployment

Only the Next.js site and Fiori dashboard are exposed publicly. CAP stays internal, improving security and reducing complexity.

Note: AWS, GCP or other Cloud Platforms are feasible

 

PostgreSQL - Managed Cloud Platform Database compatible with CAP

PostgreSQL is one of the database compatible with CAP Applications with supported documentation below:

https://cap.cloud.sap/docs/guides/databases/postgres

Beyond SAP BTP’s Hyperscaler option, many cloud platforms today — such as Railway, Render, Supabase, Neon, AWS RDS, Azure PostgreSQL, and Google Cloud SQL — offer fully managed PostgreSQL services. This opens the door for CAP applications to run cleanly in non‑SAP cloud environments while still adhering to SAP’s clean‑core and cloud‑native principles.

This flexibility is one of the reasons PostgreSQL has become a preferred choice for CAP developers building outside the traditional SAP landscape. With CAP’s built‑in PostgreSQL adapter, developers can:

• deploy CAP services to any cloud platform
• use PostgreSQL as the primary persistence layer
• maintain OData‑compliant services
• keep the application architecture clean‑core and SAP‑aligned
• scale independently of SAP BTP when needed

 

How Everything Works Together

Railway’s internal networking allows services to communicate cleanly using service names as hostnames. CAP becomes the internal API layer, while Next.js and Fiori consume it without exposing the backend to the public internet.

This gives us:

• a clean separation of concerns
• secure backend isolation
• predictable communication
• a modular system that can grow over time

It’s simple, but extremely effective — and very cloud‑native.

Conclusion: A Cloud‑Native SAP‑Aligned Blueprint

This architecture reflects how AppSkilling approaches modern SAP development: lightweight, cloud‑native, flexible, and fast to build.

By combining:

• Next.js for the public site
• SAP Fiori for the admin dashboard
• SAP CAP for the backend
• Third-party Cloud Platform Deployment and Managed RDBMS

We created a clean, maintainable foundation that powers the AppSkilling blog today and can evolve with future needs.

This isn’t just how we built our blog — it’s a practical blueprint for cloud‑native SAP‑aligned applications that blend SAP technologies with modern web development in a way that feels natural, efficient, and future‑ready.