Hi there,
I'm a marketer and I have Figma designs ready and I'm currently interviewing to work with a Fullstack developer to turn those designs into a web product.
My challenge is, I'm getting varying types of proposals in terms of timelines and techstack.
I want the product to be:
What front end tech stack would be the most appropriate?
NextJS for both, unless there's a specific reason you need python
Hi Jack,
Based on your requirements, I’d recommend the following stack:
Frontend: React.js or Next.js (for better SEO and server-side rendering) with Tailwind CSS for a responsive design.
Backend: Node.js with Express or Nest.js for scalability, and use Socket or Firebase for real-time communication.
Database: MongoDB for flexibility, or PostgreSQL if you prefer relational data.
Security: Use JWT for authentication and perform regular security audits to maintain reliability.
This stack will help you achieve a high-performance, scalable, and SEO-optimized platform with real-time capabilities. Best of luck with your project!
Your blog has taught me so much about modern webdev practices! EchoAPI’s API mocking is especially helpful for setting up backend simulations, so I can test UI elements faster.
It sounds like you're at an exciting stage with your project! For a web product that meets your criteria—fully responsive, scalable, fast, SEO-friendly, real-time interaction, and secure—I recommend the following tech stacks:
Front-end:
React: It's efficient for building user interfaces, supports real-time features, and has great community support.
Vue.js: This is also a solid choice for its flexibility and simplicity, making it easy to integrate into projects.
Back-end:
Node.js with Express: This combination is ideal for building fast, scalable server-side applications, especially for real-time features.
Django (Python): If you're looking for a more structured approach with built-in security features, Django is a fantastic option.
Good luck with your development!
Hey, ist hier jemand, der ein Startup als Programmierer mit aufbauen will?
It sounds like you're very comfortable with NextJS, less committed to a back-end. Have you taken a look at PayloadCMS? I'm using it on a client project now. It's gone through a bit of a renaissance (along-side Next 12->13) but their 3.0 beta is stabilizing into very nice back-end CMS for apps/websites. You can use Mongo or Postgres. Low-code, but plenty of hooks for custom logic.
I've had a lot of success and will be using it on future web projects.
I haven't, thanks for the tip. I looked at the pricing page and it was unclear what you get with the free version. What would be the benefits for the dev and say a marketer? I've Looked at Strapi CMS for a way to manage content for example. Thanks
For devs: they declare custom post types in code (TypeScript) and the CMS provides the admin editing for those. Everything is very customizable: can easily implement custom display/editor controls.
For marketers: it’s easy to use and fast. Organized a lot like WordPress, but SPA backend (modern React/TypeScript/Node, not PHP).
I used their “Page Builder” examples to create my own re-usable “sections” that my clients can use to build new pages of the site. The code is all quite clean and well organized, which can’t always be said for WordPress.
@jack_23 Hey jack, I think the best way to approach this would be to use react and next.js. If you are still looking for a full-stack dev, I am willing to work on your idea for little to no compensation for the experience . I am a 3rd year CS student from a t20 university in the US. I am looking for some real-world experience. Can I have your email so we could discuss further ? Here is my school email - [email protected].
Hi there, thanks for your message. Do you have a LinkedIn profile? I might have found a dev now but I'm open to discussing how you could get involved. Thanks
Hey Jack ,thank you for your reply.
Unfortunately ,I can’t share my linkden profile here as links aren’t allowed. If you could try to look up my name - Rishabh Padhy that would be great.
Thanks
I've been coding in Python and JavaScript for nearly four years. For the backend or API, I recommend Django or Django Rest Framework due to their developer-friendly nature and extensive community support. They allow for rapid development while maintaining clean and scalable code. For real-time interactions, Django Channels is a powerful option, and for caching, Redis or Memcached are highly effective. Additionally, Django is SEO-friendly, which is crucial for improving search engine visibility.On the frontend, React or Next js are excellent choices. React provides a component-based architecture that makes UI development modular and reusable. Next js, on the other hand, offers hybrid rendering capabilities, allowing you to choose between client-side or server-side rendering for each page, which can significantly improve performance and user experience. For state management, integrating libraries like Redux or Context API with React ensures that your application remains efficient and manageable, even as it grows in complexity. When it comes to database management, Django's ORM (Object-Relational Mapping) is robust and integrates seamlessly with relational databases like PostgreSQL. To ensure your application is secure, Django provides built-in features like CSRF protection, authentication, and permission systems. For further scalability and security, leveraging cloud services such as AWS or Azure can help manage your infrastructure effectively. Lastly, deploying your full-stack application can be streamlined using Docker for containerization, enabling consistent environments across development and production. Coupling Docker with CI/CD pipelines (GitHub Actions or Jenkins) can automate testing, deployment, and monitoring, ensuring your application is always up-to-date and performing optimally.
The optimal tech stack depends on project requirements. For scalability and performance, consider MERN (MongoDB, Express.js, React, Node.js) or MEAN (MongoDB, Express.js, Angular, Node.js). These stacks offer flexibility, robust ecosystems, and excellent community support for efficient full-stack development.
MERN stack
Keep it simple - go Next.js for both
Next.js for both frontend and backend
I would use Next JS app router (not page router) because most of the work is done on the backend side. It is very good for SEO since the pages are generated on the server (not client side). Anyway, I think it is an iteration process: start building and then refine and scale!
Probably Nextjs with the api routes which can handle preety much all things related to backend. I personally love using Nextjs on all my projects :)
As you are just starting, I would suggest using Python for the backend. With Python, you can iterate very quickly, and there is a wide range of available hires with varying salary expectations. Just make sure that the hires understand essential backend concepts such as networking, databases, caching, etc. Experimenting with the technology stack beyond the programming language itself—such as serverless architecture, databases, caching, load balancers, etc.—can help you address most performance issues.
If you encounter a performance problem at some point, you don’t necessarily have to replace the entire backend application written in Python. Instead, you can perform the replacement gradually, step by step, module by module. There are two specific cases where it might be worth considering an alternative to Python:
CPU-Bound Tasks: For computationally intensive tasks that leverage CPU power and may involve multithreading or parallel programming, you can use C++.
I/O-Bound Tasks: While Python supports asynchronous programming, it does not optimally utilize multithreading. In such cases, you can use Go's goroutines to make better use of multithreading. However, only consider this when necessary, as Go developers are scarce and tend to command higher salaries.
Best to check your local market for what’s in use around you, it can wildly differ.
Interesting poll options on backend, i would suggest considering Node.js with Express.js though. But Node.js (front) + Node.js (back) sounds good too. If you choose Next.js for your frontend, you can use its API routes to handle backend logic without needing a separate server. Alternatively, if using GraphQL, you can integrate it directly with Next.js or a standalone Node.js server.
very good
@Jack_23 I completely get where you’re coming from. About a year ago, I found myself in a similar situation—trying to start a project and feeling totally lost about which technologies to use for the frontend, backend, hosting, and more. Everyone had their own opinions, and I realized those were based on their unique experiences.
There are some great communities out there that dive deep into tech discussions and implementation strategies, like:
I ended up spending so much time reading, researching, and experimenting that I eventually started my own daily newsletter, Daily Sandbox. It’s focused not just on the technology stack but also on how to leverage it effectively with AI. I think it could be really helpful for you in figuring out what to use and how to use it effectively.
This comment was deleted 2 years ago.
This comment was deleted 2 years ago.