Blog
Insights, tutorials and news from the Nordic Byte engineering team.
-
Native, cross-platform or PWA: choosing a mobile app architecture
How to choose between native, Flutter/React Native and a PWA for a new mobile app, based on device access and maintenance cost rather than trend.
-
PostgreSQL or MongoDB: choosing a database for a new product
A practical framework for choosing between PostgreSQL and MongoDB for a new product, based on data shape, query patterns and team experience, not trends.
-
What a software maintenance contract should actually cover
What belongs in a software maintenance contract: support scope, response versus resolution time, retainer options, and questions to ask before you sign.
-
Serverless or containers: choosing cloud infrastructure for a small engineering team
Serverless and containers solve different problems. A practical guide to choosing between them for a small engineering team, based on traffic shape and who carries…
-
Monolith or microservices: the decision for a small engineering team
Why most small teams should default to a well-structured monolith, and the concrete signals that actually justify splitting a component into its own service.
-
Modernising a legacy system without stopping the business
How to replace a legacy system incrementally: strangler fig, splitting by domain, dual writes with reconciliation, rollback criteria, and the human side.
-
Fixed price or time and materials: choosing a software contract that fits the project
Fixed price and time and materials solve different problems. A practical guide to matching the contract model to how well-defined your project is.
-
Build vs buy: authentication and user management for a new product
Authentication looks simple until you count password resets, MFA, SSO and audit logs. A practical framework for deciding whether to build or buy.
-
Transaction categorisation in personal finance apps: build, buy, or blend
Why categorising bank transactions is harder than it looks, and how to weigh rules, in-house machine learning, and a third-party enrichment API.