将Excel工具转为Web应用：先开发Django REST API是否可行？

Absolutely, this approach is not just reasonable—it’s a best practice for your scenario, and here’s why:

Key Advantages of This Strategy #

• Separation of Concerns: By focusing on the REST API (Django models + CRUD operations: GET/POST/PUT/DELETE) first, you decouple your core business logic (the "brain" that replaces your Excel tool’s calculations and data handling) from the user interface. This means you can refine the critical data processing logic without getting distracted by UI details like form styling or layout. If you later bring on a frontend developer, they can work in parallel once the API is stable.
• Easier Testing & Validation: With the API in place, you can immediately validate your core functionality using tools like curl, Postman, or even DRF’s built-in browsable API. For example, you can test uploading Excel data to the system, running the equivalent calculations, and retrieving/modifying results—all before writing a single line of UI code. This lets you catch bugs in the business logic early, when they’re cheaper to fix.
• Future Flexibility: A well-built REST API isn’t just for your web UI. If you later need to add a mobile app, integrate with other internal systems, or even let users automate interactions with your tool, the API is already ready to go. This avoids having to refactor your core logic later to support new use cases.
• Iterative Risk Reduction: Migrating an Excel tool means you’re translating existing, possibly complex, logic to a new system. By building the API first, you can quickly confirm that your Django models and business rules match the behavior of the original Excel tool. Once that’s solid, you can layer on the UI, confident that the underlying data processing works as expected.

Quick Tips to Make This Smooth #

• Plan for UI Needs Upfront: When designing your API endpoints and serializers, think about what data the UI will need. For example, if your Excel tool has summary tables, make sure your API can return aggregated data in a format the frontend can easily display—this avoids reworking API responses later.
• Write Basic Test Cases: Use Django’s test framework to write tests for your API endpoints. This ensures that as you build the UI, you don’t accidentally break core functionality with changes.

In short, this approach is perfect for your Excel-to-web migration. It keeps your development focused, reduces risk, and sets you up for future scalability.

内容的提问来源于stack exchange，提问作者arne