I'm not technical. Can I work with iDev?

Absolutely. Most of our clients are non-technical. Just tell us what you want the end result to look like — we handle all the technical details.

How much does it cost to hire iDev?

We quote individually based on project scope and complexity. Initial consultation is completely free — we give you a clear quote after understanding your needs. No fit, no charge.

How big is the iDev team?

A few core members, each capable of delivering full-stack independently. We flexibly assign people based on project scale and can run multiple projects simultaneously.

What happens after project delivery?

We provide complete code and documentation at handover. For ongoing feature development or maintenance, we offer monthly or per-project arrangements. Most clients choose long-term collaboration.

What if I'm not satisfied with the project midway?

We confirm with you at every stage before moving forward. If the direction is off, we adjust immediately. If it truly can't continue, completed work is settled normally and all code is yours.

我完全不懂技术，能合作吗？

当然可以。我们的大部分客户都不是技术背景。你只需要告诉我们你想要什么效果，技术实现的事情完全由我们来处理。

费用大概是多少？

根据项目复杂度和功能范围单独报价。初次沟通完全免费，我们会在了解需求后给出明确报价，合适再开始，不合适不收费。

团队有几个人？

核心团队几个人，都是能独立交付的全栈开发者。根据项目规模灵活安排人手，可以同时推进多个项目，不用等排期。

项目做完以后怎么维护？

交付时会提供完整的代码和文档。后续如果需要功能迭代或维护，可以按月或按次合作。大部分客户选择了长期合作。

做到一半不满意怎么办？

每个阶段交付前都会和你确认。如果方向不对，我们及时调整。如果实在无法继续，已完成的部分正常结算，代码归你。

Spring Boot 3.4 GraalVM 原生编译实战：从入门到生产部署

Spring Boot 3.4 GraalVM Native Compilation: From Getting Started to Production Deployment

| iDev PR | 2026-08-28T09:19:29

本文详细介绍如何使用 GraalVM 将 Spring Boot 3.4 应用编译为原生可执行文件，实现毫秒级启动和极低内存占用，并分享生产环境部署经验。

This article provides a detailed guide on compiling Spring Boot 3.4 applications into native executables using GraalVM, achieving millisecond-level startup and minimal memory footprint, with production deployment insights.

为什么要原生编译传统 Spring Boot 应用运行在 JVM 之上，启动时间通常在2到10秒之间，内存占用在200MB以上。在容器化和 Serverless 场景下，这样的冷启动开销是不可接受的。GraalVM Native Image 技术通过 AOT（Ahead-of-Time）编译，将 Java 应用编译为独立的原生可执行文件。环境准备首先确保安装了以下工具：GraalVM 22.3+ for JDK 17（推荐使用 SDKMAN 安装）Native Image 组件（gu install native-image）Spring Boot 3.4.x 项目（需确保所有依赖支持 AOT）配置要点在 pom.xml 中添加 native-maven-plugin 插件，并配置 AOT 处理选项。需要特别注意的是，使用反射的代码需要提供反射配置文件。MyBatis 等 ORM 框架需要额外的 GraalVM 适配配置。Spring Boot 3.4 已内置了对大部分 Spring 生态库的 AOT 提示信息。编译与测试执行 mvn -Pnative native:compile 命令开始编译。首次编译可能需要5到15分钟，取决于项目规模和机器性能。编译完成后，在 target 目录下会生成一个独立的可执行文件，大小通常在50到100MB之间。生产部署建议原生编译后的应用启动时间可以压缩到100毫秒以内，内存占用降低至50MB左右。但需要注意，原生镜像不支持运行时动态类加载，因此所有依赖必须在编译时完全确定。建议在 CI/CD 流水线中加入原生编译步骤，并使用 distroless 容器镜像进一步缩小部署包体积。

Why Native CompilationTraditional Spring Boot applications run on the JVM with startup times typically between 2 to 10 seconds and memory consumption above 200MB. In containerized and serverless scenarios, such cold-start overhead is unacceptable. GraalVM Native Image technology compiles Java applications into standalone native executables through AOT (Ahead-of-Time) compilation.Environment SetupFirst ensure the following tools are installed:GraalVM 22.3+ for JDK 17 (SDKMAN installation recommended)Native Image component (gu install native-image)Spring Boot 3.4.x project (all dependencies must support AOT)Configuration EssentialsAdd the native-maven-plugin to pom.xml and configure AOT processing options. Pay special attention to code using reflection, which requires reflection configuration files. ORM frameworks like MyBatis need additional GraalVM adaptation configuration. Spring Boot 3.4 has built-in AOT hints for most Spring ecosystem libraries.Compilation and TestingExecute mvn -Pnative native:compile to start compilation. Initial compilation may take 5 to 15 minutes depending on project size and machine performance. After compilation, a standalone executable file is generated in the target directory, typically 50 to 100MB in size.Production Deployment RecommendationsNatively compiled applications can achieve startup times under 100 milliseconds with memory consumption reduced to approximately 50MB. However, native images do not support runtime dynamic class loading, so all dependencies must be fully determined at compile time. We recommend adding native compilation steps to CI/CD pipelines and using distroless container images to further reduce deployment package size.

← Back to News