Web development technology stack, from browser to server
We choose and build the browser, server and data layers for product teams launching or modernizing web systems. The recommendation defines where pages render, how data moves and what your engineers maintain after handover.
01Capabilities
Web systems and the responsibilities behind each
A web development technology stack combines the browser interface, server-side logic and data storage. We choose how those layers work together for these four kinds of system.
Public pages and an application in one system
We build public pages and logged-in workflows in one system, choosing how each route renders. Next.js can combine server-rendered content and client-side interaction.
Operational systems and back offices
For dispatch boards, admin consoles and reporting screens over logistics and warehouse management platforms, we define which data the browser receives and which permissions the server enforces.
Modernization of a web system you are keeping
We plan upgrades for an unsupported PHP version or an older ASP.NET estate, with the current workflows and release process in scope. Legacy modernization defines the parts to retain, refactor or replace.
Server logic, integrations and data
The rules, integrations, queues and data model sit behind the interface. We choose Node.js, .NET or Laravel around that workload and the team maintaining it.
02Stack
Full stack web development technologies
Compare the browser and server parts of the stack. The first four rows cover the interface and its engineering offer; the next six cover server platforms and runtimes.
| Page | Where it sits, and when we reach for it |
|---|---|
| React | Application stateBrowser interface. A fit for logged-in applications with interactive screens and shared state.React developmentOr book a meeting |
| Angular | Shared conventionsBrowser interface. A common approach to routing, forms and data fetching across several teams.Angular developmentOr book a meeting |
| Vue.js | Add in placeBrowser interface. Add interaction screen by screen to an application you keep.Vue.js developmentOr book a meeting |
| Front-end development | The offerBrowser interface. The engineering engagement for architecture, performance and delivery of the front end.Front-end developmentOr book a meeting |
| .NET | Long-lived coreServer platform. Business rules in an existing Microsoft estate, with maintenance shared across teams..NET developmentOr book a meeting |
| ASP.NET | The web half of .NETServer web framework. The web application and hosting decisions within a .NET system.ASP.NET developmentOr book a meeting |
| Node.js | Connected workloadsServer runtime. Work that waits on databases, queues and other systems, or keeps many connections open.Node.js developmentOr book a meeting |
| Laravel | New PHP workServer framework. A starting point for new web applications where PHP fits the system and team.Laravel developmentOr book a meeting |
| PHP | Modernize in placeServer language. Upgrade to a supported version, test the paths that take payments, then refactor.PHP modernizationOr book a meeting |
| Yii2 | Inherited estates onlyServer framework. Maintain and modernize an existing application, with migration planned around its dependencies.Yii2 maintenanceOr book a meeting |
03Fit
Choose the web system around your requirements
Rendering, existing code and the workflows you need determine whether to extend a platform, build an application or modernize in place.
| Your situation | What we recommend |
|---|---|
| Public pages a search engine must read, plus an application behind a login | One codebaseCombine React and Next.js with rendering chosen per route. Keep browser interaction and server responsibilities explicit, including who operates the server. |
| A large estate where several teams need a shared upgrade path over several years | Shared architectureUse Angular in the browser with .NET for the server, with shared conventions and an agreed upgrade path. |
| A working application you are keeping, where a few screens need to feel like a product | Screen by screenAdd Vue to the screens that need richer interaction. The surrounding application stays in place while those screens change. |
| Mostly content, editorial and marketing, with a few forms | A publishing platformStart with a publishing platform when its content model and forms fit your requirements. Our CMS and platforms overview covers platform selection and the integration or custom logic around it. |
| A PHP estate that earns money and has become slow to change | Modernize in placeBegin with a supported PHP version and tests around the paths that take payments. Assess Laravel or a rebuild against the workflows, dependencies and integration boundaries you need to retain. |
| Pages are slow, users are complaining, and somebody is proposing a rewrite | Measure firstMeasure the live system before choosing the change. Review database queries, work that could run through a queue, and image delivery to locate the bottleneck. |
Scope
We own the recommendation and the browser/server contract, with a plan your engineers can maintain. unicrew holds ISO 27001:2022 and ISO 9001:2015 certifications, renewed through a multi-stage audit with Quay Audit UK. Our front-end technologies and back-end development pages cover detailed browser and server choices. We scope delivery through web development or front-end development. For mobile apps, see mobile technologies.
We start a web build by drawing the line between browser and server. That means deciding what gets assembled where and what each side promises the other. The browser framework and the server platform then follow from that line.
Yaroslav HavrylivSenior Engineering Manager, unicrew04Delivery
Browser and server architecture, validated in one working journey
We agree the contract between the layers before expanding implementation. One real journey tests those decisions together.
- Draw the line between browser and serverWe define where pages render, what each side promises and what the interface shows when a call fails.
- Pick the server from the shape of the workWe match Node.js to connected workloads, .NET to a rules-heavy core and Laravel to web work where PHP fits. Existing skills and maintenance responsibilities shape the recommendation.
- Pick the browser side from the audience and the teamWe choose browser technologies around the audience, existing interface and the teams maintaining it. Our overview of front-end technologies covers the framework decision in detail.
- Validate one journey from browser to databaseWe build one journey from browser to database, with real sign-in, data and error states, before expanding the implementation.
05Trust
Results from web delivery and integrated systems
- Weeks to hoursUpdate release timeWaiverKing's PHP and Yii2 waiver platform: updates dropped to a couple of hours with automated tests and scalable architecture.
- 10,000-plusProducts sold in seven EU countriesJewelCandle's catalogue, now on Shopify storefronts connected to Microsoft Dynamics ERP by custom middleware, with Laravel in the stack.
- Double digit growthMaintained without a substantial increase in staffingMiniMoves order management, React over ASP.NET.
06Case studies
Web systems we have shipped, browser and server
SaaSWaiverKing: Software Development for a Waiver Form CreatorWaiverKing is a document management business serving primarily the health and fitness industries. The platform integrates with Mindbody Online, one of the largest business-systems providers for gyms and yoga studios.Weeks to hoursTime to release an update to production
eCommerceEcommerce software development for JewelCandleJewelCandle, a mid-size European manufacturer of scented products, sells across seven EU countries (B2B and B2C) via online shops.10,000-plusProducts manufactured
LogisticsMiniMoves Order Management PlatformA custom-built moving order system that simplifies booking, boosts automation, and improves operational efficiency.Double-digit growthMaintained without a substantial increase in staffingFoodtechDigital Transformation in the Food IndustryOur client is an innovation-oriented group of food companies based in Germany that produces and distributes a wide range of products for well-known retail businesses and food services.
Knowledge ManagementSaaS for Digital ResearchA SaaS solution that helps knowledge workers streamline research work involving a substantial amount of information.- ModernizationRewriting and migrating a legacy platform onto .NET Core (Global On Media)unicrew rewrote Global On Media's codebase using .NET Core, React and Stencil.js and migrated its servers in the same engagement.
07Client voices
Clients on interfaces and system ownership
Shippable and well received web GUI for previously API only application. The whole team is highly dedicated to the success of the project and delivers the planned artefacts on time. We are very happy to have chosen Artelogic.
Up until a year and a half ago, I handled all the development and support of our application myself and I needed help. I brought in Artelogic, and it was one of the best business decisions I’ve ever made.
08Questions
Questions about the whole web stack
Choose rendering per route, based on initial content, response time, crawl reliability and interaction needs.
Google can render JavaScript. Prebuilt or server-rendered HTML carries the initial content; client code handles interaction and browser state. Next.js can combine server and client responsibilities, and is one of several frameworks with rendering options.
Use a platform where its content model and workflows fit; build custom where your distinguishing logic or integrations need it.
Our overview of CMS and platforms covers the platform decision. For a hybrid system, keep the platform where it fits and integrate custom workflows around it, as in e-commerce work.
We choose the whole web system here, including the contract between browser and server.
Our overview of front-end technologies covers the browser choice. Back-end development covers the server choice. A technology can appear in more than one category because it plays a different role in each decision.
Yes. We agree the web engineering scope, delivery responsibilities and review arrangements around your system.
The plan includes the browser/server boundary and the QA practice appropriate to the work. Our managed teams include unicrew delivery coordination; the scope sets the responsibilities your own team retains.
A scoping call with an engineer. For an existing system, we ask for repository access and the requirements it needs to meet.
You receive a written recommendation on the browser/server split, the technologies to use and the parts to retain. Most engagements start within two to four weeks.
Time and materials is billed hourly and quoted per project. Fixed price is outcome based and quoted per project. Team extension is billed monthly per team member.
Plan the stack for your web system
Tell us what the web system needs to do, what exists today and who will maintain it. We will recommend the browser/server split and where a platform, custom build or modernization fits.
