Apollo

Hi all - we've built a very custom and complex application and UI using custom Vue.js + Nuxt.js, which sits on top of a GraphQL API provided by Symfony.

It's a completely custom UI for administration with lots of complex data relationships and the way we've done it has worked very well... however...

Now we need to build a second part of the system, which is a simpler CRUD style application for managing a simpler data object, but one that still has many relationships. It doesn't need quite as much flexibility, but we do need to deliver it faster if possible.

We've looked at various options, for example: - What we've got (Symfony/GraphQL/Apollo/Vue/Nuxt) - A simpler version of the above using a REST API - Symfony + API-Platform + Vue3 - Native Symfony server rendered

When we consider other frameworks, we always seem to hit stumbling blocks - my lead developer is not keen to use anything that will restrict what he can do, but I also need to consider whether there are faster / cheaper / better solutions out there.

The frameworks all seem to be able to create the code to update / delete individual data tables with ease, but make it difficult / impossible when there are complex data relationships.

Does anyone have any other ideas before we continue the way we are doing things?

Thanks in advance.

SaaS project and need to decide on a front-end framework. Will use Node.js for restful API services, and PostgreSQL for the database. Possibly introduce Prisma/Apollo if required. Infrastructure is likely to be AWS. This is a business to business SaaS project, not the consumer. 1-2K potential org subscribers, where the orgs are small businesses with 1-15 employees. The product would be used daily, mostly serving the North American market. I'm struggling with what front-end framework. I lean towards Vue.js/ Nuxt.js as it's what I have the most experience with, it's an easier learning curve for new inexperienced developers, and it had great growth in recent years. However, React/Next.js are established frameworks, with a larger community but a steeper learning curve (if I can't get intermediate to senior react developers) and I haven't worked with it. I'm looking for not answers, but advice from the community regarding what other factors I should be considering when deciding. This is a new project (not a re-write of an existing one). Appreciate everyone's feedback.

I am working on a production-ready website, and I need to fetch data from a GraphQL API built with Apollo Server. I would like to use Relay, due to performance optimizations, but the docs are too complicated, and the community is not as extended as Apollo's one. If anyone has used both tools or has faced similar questions, I would really appreciate your comment and your opinion on this.

Note: I will also be using Next.js with Static Site Generation, which provides multiple performance optimizations.

Im getting a empty object [] or [ ] in my console, my getPosts is working in my MERN+Apollo/GraphQL Stack, but..... not the others, the fields are showing in my getStop, getItems, but its not showing the data from MongoDB

We want to build an e/m-learning platform, so please guide us on choosing Quasar Framework or Vuetify? Our preferred tech stack is - Vue.js, GraphQL, Apollo. Which is best suited for the production-level UI framework?

We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

• Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
• Vue Styleguidist as our style guide and pool of developed Vue.js components
• Vuetify as Material Component Framework (for fast app development)
• TypeScript as programming language
• Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
• ESLint, TSLint and Prettier for coding style and code analyzes
• Jest as testing framework
• Google Fonts and Font Awesome for typography and icon toolkit
• NativeScript-Vue for mobile development

The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

• Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
• Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
• Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
• Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
• Large scaling. Vue.js can help to develop pretty large reusable templates.
• Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.

At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.