Stack Advice

Being a Laravel dev (I've used ASP.net too), I would hands-down recommend Laravel. It's convenient to build on, easy to deploy, and there are plenty of skilled Laravel engineers in almost every country. So if you ever want to bring development 'in-house' or work intermittently with freelancers after you've finished with the agency you're working with, you'll find that quite easy wherever you are.

As has been mentioned, Laravel is very ergonomic for developers and it has an incredible community (mostly filled with really positive people) and ecosystem (lots of ready-to-use open source packages to augment your application with new features).

Development costs for the two I'd expect to be about the same, but possibly the agencies using .net will charge a little more as it has historically commanded a slightly higher price point, but I'm not sure how true that still is.

Both will get the job done perfectly well. Laravel would be my choice.

I love .NET, and have a bit of experience in Laravel (nothing in production though). I would recommend sticking to Laravel for a project like the one you want to do. It is loved by developers for its elegancy and features. Laravel has incredible ecosystem with many packages available to implement features fast and easy. The development cost will be much less than .NET (PHP developers are cheap).

What about maintenance? It is a different story. PHP doesn't scale as well as other technologies, but it will have no problem handling traffic for a website like that.

I would recommend Firebase for this as it has an amazing SDK with pretty much everything you need out of the box. Depending of how 'realtime' your project needs to be, you can go with Firestore, latency is a bit higher than Realtime DB, but price is much lower. The combination with Node, using CloudFunction, will streamline your process having it all under the same roof.

You should consider the support of your target realtime stack. Does it support for both your clients side(device and user) SDKs ? If not, you have to handle the realtime from one side by combine several stacks

As a Laravel developer, I'd have to say go with Laravel. Although you can move away from PHP, it means any of that legacy code will still need to be completely ported to Java or whatever other language you use. Whereas, staying with PHP, you may find it easier to re-use/adapt that existing code.

Of course, if you're going for a full rewrite, then that might not be a useful consideration. However, even a full rewrite will introduce a lot of changes. When having to do this kind of thing, I recommend changing as few things as possible at once. So staying in the same language while upgrading may keep some pain points down.

Vue.js with PHP/Laravel (vue.js is much better than Angular for building the frontend. I feel much cleaner and faster). you already using MySQL database PHP is prefered.

Hi Kelechi,

It is pretty easy. You will need to create and express.js API with Nodejs and have the Postgreql in it. Then you can create your Vue Apps and connect to the express API. This will help; https://www.youtube.com/playlist?list=PLWKjhJtqVAbnadueQ-C5keMQQiQau_i0D

I used a similar setup but I wouldn't recommend it except if you absolutely must. Use something like NuxtJs.

I do not recommend Vue for a job, learn React or Angular

Additionally Typescript for React is a wise choice. however, you can start using Javascript.

The open source web framework Express.js for Node.js enables programmers to create online apps and APIs. It offers a number of tools and functionality, including as templates, road handlers, renderers, and debugging tools, to make development simpler. The popular Express.js substitutes Koa.js, Hapi.js, Fastify, and Restify are also available.

8+ Hour Stream - 3 Giveaways - Build a Full Stack Forum with Node/Express/Postgres/Vue.js/Bootstrap https://www.youtube.com/watch?v=aqiJQaPDy7o

Look for tutorials on how to build a website, but don't get too caught up in the stack, it doesn't matter at your level. Just have fun, that's my suggestion. If you need some help, feel free to add me on discord

Sergueiovitch#4089

Since the code is python, pycharm is lighter on resources, and there is no need to use the full Intellij IDE.

The project management is easier in PyCharm and for a sample project you probably don't need the complex project management in intellij. I definitely wouldn't use two IDEs at the same time, unless you got too much machine capacity and like more complex interactions.

My Advice to you complete the Css 3 first then practice practice practice more and more then go toward to learn JavaScript then after that you become front end but there are some decorators you missed it but don't worry , then select language to learn it to back-end so i suggest for you python more powerful and easy to learn and don't take time to learn it (basic, practice on it some projects, then learn OOP using python on freecodecamp then make 5 projects, then learn DSA, finally enter DB and select flask or django then link between front-end and back-end)

You can always bet on JavaScript, you say that you want to be a full-stack developer, so you will never go wrong with that. For a path I would recommend choosing a project you want to build, as many programmers say - "Everything will eventually be built in JavaScript" - choose a project and try to jump right into it, see as many references as possible, watch youtube videos, but most imporantly!! Build something you are passionate about and have fun! :)

There are sssssooooo many good options for deploying a web service to production, there is really no space here (or probably anywhere outside a dedicated year-long course) to learn all the necessary technologies for even a part of this huge space. So instead - lets start with the easiest one (IMHO, others may disagree): AWS Fargate.

AWS Fargate is a simple container runtime - there are others, but Fargate excels in that it is very simple to create and manage (you basically let AWS manage it for you) and you don't need to worry about servers and control nodes and proxies and other things other container runtimes (such as Kubernetes) will have you worry about. On the other hand, it does not skimp on performance and if you ever want to go Kubernetes (which is all the hotness these days) - there is a clear and simple "upgrade" path.

How do you get there? First learn what a "container" is - the concept was popularized by the Docker product and it is pretty much an industry standard (there are other container formats, but the Cloud Native Foundation's format is basically the Docker format) - a container allows you to bundle an application in an lightweight operating system image and run it as an application. A container runtime can then take a container and run it, scaling it up as needed, without you needing to manage deployment scripts, process management and stuff like that.

To deploy your Java web service on AWS Fargate you need to do the following:

1. Package your Java web service in a JAR file. Maven is the common tool to do that, though gradle is also very popular. There are other build tools for Java but you probably want to choose one of these two and learn it. Gradle is somewhat simpler to start with but it gets complicated pretty fast (it is basically a scripting language for building with a lot of "magic" - which often implies a stiff learning curve). Maven looks more daunting at first - with all that messy XML to read and write - but its internal complexity peeks really fast and then adding new functionality is basically just using (or creating) new plugins with the same simple configuration language.

2. Create a container image from your JAR file that can run it as a container: You obviously need to learn Docker and how to write Dockerfile scripts - this is pretty easy and straightforward, then look for examples how to run your specific application in a container - depending on which Java framework you're using. My weapon of choice is Vert.x and here's the documentation for that on Docker: https://vertx.io/docs/4.3.7/vertx-docker/. If you are using Maven then you can use a plugin to automate building the container image for you - but you should still learn how to do it yourself to understand what's going on. I use com.spotify:dockerfile-maven-plugin (it is very simple and stable but also have stopped development) or you can use io.fabric8:docker-maven-plugin which is newer and more capable but also more complex. You may be able to use these with Gradle as well - I don't have any experience with that.

3. Create an AWS account and learn about setting AWS Fargate and AWS Application Load Balancer (you should use an AWS load balancer to expose your Fargate service to the public internet - the alternative is at best much more complicated and at worst unreliable). AWS has a lot of good documentation on the subject. You can start by setting everything up in the AWS console, but you should really learn how to do it with the AWS CLI tool and also recommended to use an automated provisioning tool such as AWS CloudFormation or Terraform. The advantage of using Terraform is that it is not AWS specific and if you ever want to move to a different provider, you can take Terraform with you, OTOH it is more complex to learn and operate.

4. Set up a continuous integration (CI) pipeline to automatically build and deploy your service. There are many good options, but you should probably stick with what your source control service provides: Github Actions, Gitlab CI, Bitbucket Pipelines, Azure DevOps or maybe even AWS CodePipeline (if you already use AWS you might want to go full in). AWS also has a full git repository hosting (AWS CodeCommit) and integrated CI/CD (AWS CodeStar) so you can keep all your eggs in one basket - they do make it very simple and easy to maintain and control, but the standard caveats about eggs and baskets apply.

5. Deploy your service and then monitor it - this is a completely different huge ecosystem that you'd need to know about when you actually need to maintain a "real" production service. I use StatusCake (for external status monitoring), AWS CloudWatch (internal status monitoring and alerts) and OpsGenie (on-call management, alerting and escalation).

Hello,

As for hosting the front-end, the choice would be Vercel. Super straight-forward non-nonsense deployment. As for Java, I'd package it in a Docker container, and deploy it this way.

There are multiple options for deploying Docker containers: Azure, GCP, and AWS will have them, and there's very little to no difference between them. From some tests I have seen, Azure and AWS are faster than GCP.

Given Angular is written in TypeScript, C# will feel more familiar to you. Other reasons to choose ASP.NET are that it's one of the fastest frameworks out there for any language, has a lower learning curve compared to Spring Boot, allows you to quickly build JSON Web APIs and uses less memory. Another notable option if you have a lot of TypeScript code you wish to reuse is Nest framework, which is a TypeScript framework that uses the same architecture as Angular but for back end APIs. I would still choose ASP.NET over Nest but it depends on what will give you more benefits.

Given you have cross platform experience (dart, angular) I would recommend spring boot. It is a powerful platform, allows you to easily integrate with many standard tools: databases, message queues, … And you have the freedom to deploy your applications on every platform that has Java or containers available - so virtually everywhere.

I would advise you to learn a good amount of Javascript and/or Typescript. Start with one or the other. Then, start learning a framework like Vue or React (I'd recommend the latter), and if you've gained enough knowledge about core topics, get on to learn a meta framework like NextJS (which is based on React).

For styling, I would recommend to learn at least the basics of CSS before you move on to a framework like Bootstrap or Tailwind. You mention you already have so that's good. I would definitely invest time in understanding Grid and Flexbox, as well as writing media queries for responsiveness if you haven't so. When you're confident writing your own CSS, I could definitely recommend Tailwind as framework as that still allows you to implement your own styling and designs, instead of using a predefined UI Component-based framework like Bootstrap. I've been using it for a few months now and when you get the hang of it, it's really time efficient.

One tip: try to define your tech stack now, and focus on mastering those tools instead of being a jack of all trades. It's hard to master tools/topics if you're not enough invested in learning those because you want to learn too much. For example, I would either pick Django or Flask in your situation. My preference goes to Django. If API support is needed, then use the Django REST Framework for example.

Also, best way to learn is to just build things. Try building your portfolio website or a to-do app. Also, try to build something that retrieves data from an API.

Prototype to code would be better with teleport.hq. Figma is ok for the prototype itself but to get the code you would still end up using the Teleport plugin. Either way the code generated is always moderately hacky, you should keep learning JS and HTML so you can fix up odd looking parts yourself.

If you're building apps with machine learning libraries that are not available with pub.dev (ie. scikit learn, keras) on flutter, you are better off building with Kivy. For every other scenario, Flutter is miles ahead. Be it performance, UI components, customization, scope, type safety, speed, stability, native implementations of libraries like notifications, maps, payment systems, local storage etc. Not all python libraries are compatible with ARM that runs on most smartphones. Flutter now has support for certain tflite models that can run ML algorithms.

Our organization uses Flutter in the front end and a combination of Python and JS along with Firebase in our backend. I would recommend the same. Don't reinvent the wheel, use the tools best available and supported.

Just an FYI: don't do flutter tutorials online. Watch one and start making your apps, trust me you'll figure it out yourself and will be able to pick it up by doing.

Flutter is better it's easy to learn, build fast in both Android and iOS.