Trending Feed

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

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.

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.

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.

I would suggest instead of going all over, you should focus on one specific field you want to master. I also have prior experience with all of these languages and during my studies, I can understand the mess you are going through.

In the end, I would say you should go with JavaScript, here are the Libraries/Frameworks you can use. - WEB DEVELOPMENT : Frontend: React, Angular, Vue - Backend: ExpressJs, NestJs - MOBILE DEVELOPMENT (IOS & Android): React Native - IOT : Socket.io - DataScience : TensorflowJs

Best of luck with your studies.

If you will be studying c# checkout A ASP-NET core, MAUI - mobile cross-platform, and if you have time look at Blazor and Entity Framework.

Hi Brian,

Dom here, co-founder of Five, a low-code company.

The first question I'd ask is this: do you want to continue using Google Sheets or Microsoft Excel as your database? If yes, then indeed Retool is a great choice because it connects to Google Sheets and lets you build a front end on top of it. An alternative could be AppSheet, which belongs to Google and does the same as Retool.

My advice, however, would be not to use a spreadsheet as a database. I won't go into all the reasons for this. But a spreadsheet is not designed to support web applications. At some point, it will either become very slow or you will struggle with data integrity, especially if you have ten users reading & writing data concurrently. That's why I'd look for an online database application builder.

Now, this is where I'm biased, given my role at Five, but here's what Five lets you do:

You can create your own MySQL database straight inside Five. So instead of storing data in a spreadsheet, you store it in a web-hosted MySQL database. You can import CSV files into your database, so your existing data won't be lost. You can then build the front end on top of the MySQL database. The advantages: you get something that is scalable and won't break in the future. And MySQL is open-source, so even if at some point in the future, you won't go elsewhere with your application, your data is portable.

Hope this helps and as I said, think about the right back end for your application first. :)

Dom

Hi Brian! Based on your requirements, I’d strongly suggest giving Retool a try. It excels at having the pre-assembled components library which lets you put together apps in a breeze. It scales with your needs and the medium plan should be quite sufficient for a while. I’m helping companies with their use of Retool as part of my business: www.blackholeconsulting.net

Hope this recommendation helps! Cheers, Stephan

I would highly recommend using your cloud provider CDN whether this AWS, GCP or AZure on top of your object store SO, GCS or Blobstore. It will greatly reduce the cost while maintaining speed and performance. For image compression https://github.com/imazen/imageflow is amazing plus it's written in rust which really helps with safety and speed.

Hello, We have been at similar situation like yours. We deal with serving around 1TB of images for one of our client, and it skyrockets the price way too quickly if we are using any cloud provider services. If and only if you have time or devops people to spare into research I'd recommend setting up your own CDN service in one/multi cloud provider. In my experience going with custom built solution is cheaper. We are using this https://github.com/ilhaan/kubeCDN , it's a CDN cluster setup on k8s cluster.

For image compressing, we have our inhouse library to compress images without losing much resolution making it almost impossible for regular human to detect changes. (Github link)[ https://github.com/Comet-App/CImage ].

Testing and benchmarking are always messy, cause in our case we can't scale it with existing tools so we simulate acutual 10k req on client's platform. For individual scores, we prefer (GTMetrix)[ https://gtmetrix.com/ ] and (loader.io)[ https://loader.io/ ]. We are also working on custom multiregion supported webpage/api benchmarking platform, will share with if you're interested.

Great stack. Very productive and the vue development tools are excellent. The generic views from drf help a lot in productivity

Easy stack to start and develop your product. Vue is easy to learn and use, great support from the community if you have questions. Django is a powerful backend framework, the Django Rest Framework comes with a lot of generic views that you can use which will come in handy. Also, Django admin gives you and out of the box interface for all your admin/support needs.

Although I use Hugo instead of React (and don't have experience with Ant Design), I'd highly suggest using Tailwind. The main reason I like it is because I can't tell if a site is using Tailwind or regular CSS, whereas once you've seen a Bootstrap site, you'll see Bootstrap everywhere whenever it's used (and I'd assume the same with Ant Design).

Most probably you don't want to create component's logic from scratch. As you already have an app, try to make a list of all components that you'll need - modals, dropdowns, etc. And then try to find a library that has all of them, because some components are rare (like a range selector).

There's some libraries built with/for tailwind, for example https://headlessui.com . It's pretty basic, but maybe it'll be enough for you.

It's not that when you're using tailwind you're not touching css. It's just a convenient way to write it and it gives you a nice design system by default.

I'd recommend to learn Spring as it is very widespread in the industry and provides a lot of easy integration into most of the common backend tech stacks. Rather than learning Java you could look into Kotlin. It's a very consistent, stable and well-thought language in my opinion and not as verbose as Java. Many problems can be solved with Kotlin in a clear and elegant way while also always having the option to use data structures and libs in JVM. It is also has a very good support in Spring.

Why not pick Django or Flask (both Python)

Hi Ravi - I spent 5 years at Twilio and am currently over at Messagebird (CPaaS). - Generally, there are two options: - use SMS API and own the logic on your side (Phone number provisioning, token creation, token validation, retries, fallback etc.) - Verify Solution (which both Messagebird and Twilio offer): Verify provides a purpose-built API. Number provisioning (especially challenging globally), token creation, retries, fallback methods, etc. are managed by the verify solution

Messagebird helps the largest senders with use cases like OTP globally, and you have the choice own the development, or use the Verify API. Anecdotally, our Global network, and the maturity of our network, makes us stand apart in regards to global reach and deliverability.

Happy to chat, feel free to reach out.

Hi there, Ravi! Full disclosure: I used to work for Twilio.

User experience and developer experience are the primary reasons I'd recommend Twilio. Starting with user experience:

• Simplicity : There's a reason companies with great engineering talent (like Stripe and Shopify) hand off the implementation of scalable 2FA infrastructure to Twilio - it's because they see improved user conversions and experience, by leaning on the dedicated Verification team at Twilio.

• Reliability : Twilio has been building out even more regionalized infrastructure the past two years for improved service reliability. The Verify service also optimizes the telecommunications providers + sending phone numbers that are used if they ever detect lower-than-usual 2FA conversion rates (if they measure that users aren't entering 2FA codes at normal rates, they automatically route traffic differently to improve and ensure messages are getting delivered).

On the topic of developer experience:

• Ease of integration : I worked with customers who had MFA proofs of concept running in one afternoon. Twilio has easy-to-understand documentation and code examples to get started in a variety of languages: https://www.twilio.com/docs/verify

• Extensibility : As you mentioned in your post, you're considering SMS and Email channels for MFA today, but want to keep your options open for improving security and UX. Twilio already offers additional verification channels , like Voice, in-app Push Notifications, and TOTP integrations with authenticator apps like Authy and Google Authenticator. For additional security considerations, Twilio's Lookup API v2 provides a useful database of information about users' phones, to complement your MFA implementation.

• Maintainability : Twilio has a solid track record for improving its Verification & security solutions since they've launched them, and last I knew while working there, planned to continue to invest strategically in these offerings.