APAX aims to solve unique problems with custom solutions. Rather than reinventing solutions, the team aggregates the best available tools to work toward client goals. Every application requires what developers call the tech stack, made of various layers, each bringing distinct decisions that vary by project.
The Tech Stack is Complex
Each tool deserves analysis considering: implementation costs, upkeep expenses, security and compliance needs, existing code integration, mobile requirements, scalability importance, and flexibility for future changes.
The solution comprises several layers often broken into four components: frontend, backend, database, and deployment process. Each deserves thorough questioning and communication.
Frontend
The frontend handles user input and communicates with the broader tech stack. Key questions include: What is the core content? How much will it change? Why must it change? How frequently? Who manages content? Will there be a mobile experience?
Backend
The backend stores and retrieves data from the database, invisible to users. Questions include: Will there be non-standard data models? What data processing levels are needed? How often will models change? Will frequent security or compliance updates be necessary?
Database
The database stores and maintains organized data relationships. Consider: Will the application require intensive searching? Will it need future scaling? How much data will it handle?
Deployment
The deployment pipeline delivers code to users as new functionality. Questions include: Is there an existing deployment strategy? Are enterprise services already in use? Will there be a mobile app? Is automated testing important? What user load is expected?
A Recent Experience
Aquatic Remedies
In 2019, APAX completed a project for a company needing better information dissemination across geographically dispersed employees. The challenge involved building a minimum viable product expandable in later phases while meeting budget constraints.
Key decisions centered on frontend and backend approaches. For the frontend, the team chose Expo, a mobile framework enabling a single codebase for both iOS and Android devices. For the backend, they selected Drupal, a content management system better suited for frequent content updates than their typical approach.
Help Us Choose the Best Tech
Effective tech stacks require careful consideration. APAX recommends asking consistent questions across development.
General Questions
- What is the tech stack?
- What tools are planned? Why?
- What other tools were considered? Why rejected?
- Do additional upkeep costs exist?
- Have similar problems been solved before?
- Does the team have experience with these tools?
- Will this technology scale appropriately?
- Is this technology commonly used?
- Do you already pay for tools solving parts of this problem?
Frontend Questions
- What is the core content?
- How much content will change?
- Why must it change?
- How frequently will it change?
- Who manages content?
- Will there be a mobile experience?
Backend Questions
- Will there be non-standard data models?
- What data processing levels are needed?
- How often will data models change?
- Will frequent security or compliance updates be necessary?
Database Questions
- Will the application require intensive searching?
- Will it need future scaling?
- How much data will it handle?
Deployment Questions
- Is there an existing deployment strategy?
- Are enterprise services already in use?
- Will there be a mobile app? Which devices?
- Is automated testing important?
- Are network administrators available?
- What user load is expected?
Conclusion
APAX’s role involves asking questions consistently throughout development. By involving clients in technical decisions, we create solutions that everyone values. Not all questions apply universally, and unique problems may require adapted approaches. The primary goal remains selecting the optimal tech stack, which evolves as requirements emerge.
What questions would you add? Are any unclear?