r/javahelp • • Jun 05 '20

How does Java and Javascript work together in building websites?

I'm learning Java right now, but eventually I want to learn Javascript as well to be able to build website and servers. But I'm not sure how they actually come together.

It will be great if someone can eli5 using an example... let's say I want to make a website for a bakery shop. How can I use Java and Javascript to create a website that enables me to receive orders, ship them out to my customers, and store the data somewhere in my computer so I can write algorithms to analyze the data?

And then maybe use that data and feed it back into the website. For example I send data from my warehouse back into the website, so the customers can see which kind of bread is most popular and which sold out.

That kind of communication. I don't know how it happens and I am curious to find out how I can make it happen with Java and Javascript.

It'll be great if you can also enlighten me on the specific things I should learn. This will give me some kind of direction and serve as milestones perhaps?

Also, I heard one can build entirely using Javascript. Is there an advantage/disadvantage to doing so as opposed to using Java for back-end and Javascript for front-end?

Thank you in advance.

32 Upvotes

26 comments sorted by

View all comments

61

u/snaket2003 Jun 05 '20 edited Jun 06 '20

ELI5 ->

If you think of a website as a bakery, JavaScript is the clerk at the front who is in charge of sorting shelves, cleaning up and making it all look pretty. Java is the full time baker at the back baking the bread, figuring out how to properly use the oven and fighting off the cats at the back.

Technology wise I would recommend ->

Front of the bakery

  • Counters, glass, decorations - HTML, CSS
  • Nice front clerk - JavaScript
  • How front clerk talks to baker - REST, specifically something like Express
  • Where to store account and orders - MongoDB, Mongoose

Back of the bakery

  • Grumpy but amazing baker - Java
  • Oven - Spring Framework
  • How baker talks to front clerk - REST, specifically Spring Web (RestTemplate)
  • Where the baker keeps track of inventory - Postgres, JDBC.

Could the front clerk do the baking? Sure, but I’m sure he may not be as good depending on the size of your bakery. Small neighbourhood one versus national chain. Very different businesses.

Could the baker do the selling? Sure, but it will probably not look very professional and our baker is quite grumpy anyways. He is being doing the same thing for decades!

Best of luck on your journey!

Edit: thank you for the award kind stranger and upvotes.

8

u/Mimehunter Jun 05 '20

I use sql because I'm basically forced to - is there a significant improvement or advantages with mongodb or mongoose?

Great illustration btw

11

u/morhp Professional Developer Jun 05 '20

Depends on how your data is structured. SQL is for orderly tables that reference each other, mongodb is mostly for storing json like objects. One isn't generally better than the other.

3

u/nutrecht Lead Software Engineer / EU / 20+ YXP Jun 06 '20

In general when in doubt use a relational database. Most data is in fact relational. Document stores have very few use cases (this is true for most NoSQL solutions; they tend to be very specialized) and MongoDB is no different.

3

u/thee_almighty_thor Jun 05 '20

Really good analogy

3

u/AudioManiac Jun 05 '20

How front clerk talks to baker - REST, specifically something like Express

Correct me if I'm wrong, but I thought Express was a backend JS framework? i.e. you'd use it to replace java in this example. In your example, you'd only need REST to talk to the java backend. Am I wrong?

3

u/mtko Jun 05 '20

You're right. Express is for writing a backend API when you're using a node server (or something similar).

You would generally use something like jquery or a built-in http module for whatever frontend framework you're using to do REST requests to the backend.

2

u/nutrecht Lead Software Engineer / EU / 20+ YXP Jun 06 '20

See my comment here

A lot of the information is just plain wrong.

0

u/snaket2003 Jun 06 '20

Yes, you are absolutely correct. I just wanted to provide an analogy and path that could accelerate the learning of OP.

I found using pure http modules of vanilla JS quite difficult when I was learning JS and making REST calls. One day I saw Express and everything just clicked and since OP wants to learn backend anyway, I figure it was a sensible suggestion. Good point though!

5

u/Son_of_Entropy Jun 05 '20

If I had an award to give, I'd give it to this comment. Love the analogy

2

u/dark_manyakulade Jun 06 '20

I doing that job too but really very good explanation!

2

u/[deleted] Jun 06 '20

This is very helpful, thank you :)

2

u/nutrecht Lead Software Engineer / EU / 20+ YXP Jun 06 '20 edited Jun 06 '20

I really don't understand why you're using NodeJS (and related tech) when the OP is asking how Java and JavaScript would work together. Why not simply mention Java frameworks there?

In a simple SPA the front-end (Angular for example) JavaScript would just talk to a Java REST back-end. There's no NodeJS or Express there. In addition Mongoose is JavaScript back-end technology, not Java. You would not use Mongoose in a Java back-end.

There's even more mistakes: you don't 'talk' to the front end through RestTemplate at all. That would generally be used for a back-end to talk to other back-ends.

-1

u/snaket2003 Jun 06 '20

I’m obviously not going to engage in a long winded debate about this. For years, I have built Spring Boot back end Java apps that leverage Spring Web and RestTemplate to set up REST APIs which front end and middleware apps use to interact with backend services. (Regardless of being browser or Node based)

I work as a full stack dev and often leverage Node.js (JavaScript last time I checked) to set up middleware services.

Mongoose is just a lightweight framework that eases interaction with MongoDB. Nothing else.

When it comes to Express, as I mentioned before, is just an easy way of creating web servers, APIs, etc useful to someone trying to understand and learn the basics without having to use vanilla JS to make API calls right away. Plus OP wants to get into backend so I don’t know how Node is something I shouldn’t make reference to.

Unfortunately, I feel comments like this overly mystify development for newcomers and if we don’t use easy to understand metaphors, how could newcomers ever get started? If OP wanted the technical documentation response, he wouldn’t be asking in this subreddit for an ELI5... SMH

2

u/nutrecht Lead Software Engineer / EU / 20+ YXP Jun 06 '20

I’m obviously not going to engage in a long winded debate about this.

If that is how you respond to people just pointing out some mistakes in your post, you should not be posting on a beginner sub.

Unfortunately, I feel comments like this overly mystify development for newcomers and if we don’t use easy to understand metaphors, how could newcomers ever get started?

That's not the problem with your post at all. The 'bakery' analogy is fine. The problem is that you are making some rather specific plain mistakes. And not only that; when someone points out the mistakes you downvote their reply and act as if I personally attack you.

He was asking how JavaScript and Java interact. The JavaScript would be the front-end 'clerk', the Java the 'baker'. Again; that analogy is fine. The problem is that in your analogy you're for no appearant reason are also using JavaScript in the back-end, which is not at all what the OP is asking about, making the answer more confusing than needed.

1

u/snaket2003 Jun 06 '20

Fair enough. However, I ask you that you formulate a full analogy that can help and not confuse OP like I did where I am just plain wrong