Skip to main content
FomiVIP
INSIGHTS

Insights

Industry insights, technical sharing and service cases. We write down the pitfalls and methods from our projects, hoping they help you in your own digital transformation.

Selected work

项目界面

交付过的真实界面,左右切换浏览,点击可放大看细节。

Industry Insights2026/11/05

IT Projects: Why We Recommend Diagnosing Before Building Systems

Many projects start by comparing systems and features, only to stall later on disconnected data. Spending two to three weeks up front mapping the business workflow and master data often saves months of rework down the road.

阅读全文
Tech Sharing2026/11/05

How to Keep Shipping System Updates Without an In-House Tech Team

From recruiting on your behalf and staff augmentation to hosting an entire dedicated team, different gaps call for different engagement models. The key is to be clear first about what you need: a person, a team, or stability.

阅读全文
Service Cases2026/11/05

After Go-Live: An Actionable Operations Handover Checklist

Delivery isn't the finish line. Whether the documentation, accounts, backups, monitoring, and emergency paths are all in place determines if the system can still be maintained with confidence six months later.

阅读全文
Industry Insights2026/10/09

The One Line on Our Quote That Hasn't Changed in Ten Years

Our 2016 quote vs this year's: new format, more items, new prices — one line untouched: "Once requirements are confirmed, scope changes are quoted separately." It has saved us more than once and been called rigid too. It promises nothing; it just says changing scope means pricing again.

阅读全文
Tech Sharing2026/08/21

We Added One Rollback Line to Our Gray Release Script

Our gray release script ran two years without incident — until August, when a styling bug appeared on older Android after ramping to 50%. The script could only advance, never retreat; manual Nginx edits cost 12 extra minutes. We added a rollback command that runs the same checks as advance.

阅读全文
Service Cases2026/07/10

Rebuilding the JunliYigou Points Module: A New Idempotency Key

The JunliYigou points system ran seven years on an idempotency key of order ID plus type. New sources — sign-ins, reviews, manual compensation — broke that key. We restructured it into source + biz_id + change_type and backfilled 400,000+ historical records in a 2-hour run.

阅读全文
Industry Insights2026/04/17

The 5 Questions Clients Ask Most at Maintenance Renewal

Three years of meeting notes show renewals come down to 5 questions: who's responsible next year, can responses be faster, why the price change, will the system change hands, is the old data still there. We turned them into a one-pager sent ahead of meetings, and the meetings got shorter.

阅读全文
Tech Sharing2026/03/06

Redis Caching and Rate Limiting for Expo QR Signup Peaks

Expo QR signups peaked at 600+ submissions per minute — with no extra machines. Three layers: Nginx per-IP rate limiting, Redis signup state with debouncing, and an idempotency key before every database write. Static pages on CDN, submissions on a separate domain. Three hours on-site, zero 502s.

阅读全文
Service Cases2026/01/16

Fresh Market Opens at 5 a.m.: Tracking Down an Order Timeout

A fresh-grocery mini-program opens orders at 5 a.m. One morning, timeouts piled up to 40+ failed orders — not concurrency, but a scheduled aggregation job that slipped to 4:55 and dragged MySQL down. We moved it to 3:40 and gave it a read-only replica. The morning rush has not stalled since.

阅读全文
Industry Insights2025/10/31

A Client Asked If They Need Kubernetes. We Looked at Daily Active Users

"Should we adopt K8s?" We ask three numbers first: daily active users, machine count, deploys per month. Answer: ~3,000, 2 machines, 2 deploys. We didn't adopt it — Jenkins pipelines, replication, and backups were enough. Six months later, DAU had tripled; only then did we migrate together.

阅读全文
Tech Sharing2025/09/19

MySQL Index Tuning: A 3-Table JOIN From 4 Seconds to 0.3

A five-year-old reporting query — a 3-table JOIN — had crept to 4+ seconds at month-end. No sharding, no caching: EXPLAIN showed a missing index, a poor JOIN order, and a filesort. Two composite indexes, a pinned driving table, and a query rewrite brought it to 0.3 seconds.

阅读全文
Industry Insights2025/08/08

Cutting a Visa Form From 17 Fields to 9

The 2016 paper visa form went from 17 fields to 11; the 2025 rebuild brought it to 9, 6 required. What changed was capture: name and passport number from OCR, birth date and expiry from the machine-readable zone. We studied 300 old applications first to see which fields were never reviewed.

阅读全文
Consulting · Free initial chat

Have a specific question to discuss?

For situations not covered in the articles, feel free to share your context directly.

Contact us

Mon–Fri 9:00–18:00 · We respond on business days within one business day.

WeChat (Business Only)
WeChat (Business Only)二维码

Scan and add our WeChat for consulting

Or fill out the requirements form