Lets Start Journey Of Web Development

Career Path

HTML-HTML5
CSS-CSS3
Bootstrap-adv.Bootstrap
Javascript-ES6 JAVASCRIPT
ReactJs library
NodeJs
- Mediaquery
- Bootstrap readymade
Performance Optimization{3sec}
Web Accessibility-Make app for everyone for disabled also
PWA- progressive web app-less Mbs
- AWS
Devops
Typescript-Microsoft uses Typescript for new projects
Web assembly-Performance optimizer
GraphQL-How to communicate with server

#	Subject	Syllabus	Weblinks
1	Web Development	Otto	dd
2	hi	Thornton	@fat
3	Larry	the Bird	@twitter

Can you give me ideas of what to build for job?

Now we are talking. Here are some examples that would qualify:

Social media application (Twitter, Facebook, etc.)
E-commerce application (Amazon, Flipkart, etc.)
Media player (Spotify)
Productivity app (Trello, Asana, Evernote, etc.)
Messaging app (WhatsApp)
Booking app (MakeMyTrip)

Whoa! Wait. Wouldn't every project take a lot of time then?

Yes, it takes time and commitment to make good projects. The reason why software salaries are good is there's a shortage of supply of good developers. Most of you reading this wouldn't do it. If you do it, we'd be happy to elevate you into a good full-time job. Glad you're reading further. Let's go deeper into a good project.

What features should I aim for?

For any app, you can classify a feature into core (without which the app cannot function) and auxiliary (which helps in the core function). Let's take the example of an e-commerce app. The primary goal of the app is to place an order. Here are some features along with their categorization:

Product Listing - This is a core feature. You cannot place an order without seeing the list of products.
Address Input - This is again a core feature. Without your address, the order can't be shipped.
Checkout Flow - This is definitely a core feature.
Wishlist - Now this is an auxiliary feature. If you can't add a product to wishlist, it doesn't hamper your ability to place an order.

Here are some examples of goals:

Social media application - Share what's on your mind and see what others are doing
Media player - Play a song/video seamlessly
Productivity app - Add to-do items, assign deadlines, get a sorted view of everything that needs to be done
Messaging app - Able to chat with someone, i.e. messages should be sent and delivered very fast
Booking app - Find a good deal (search by your location, add filters, book a trip)

What technical features should I showcase?

Okay, let's talk in quantifiable terms now. Your app should:

Be a Single Page Application (SPA) If you haven't heard about SPA yet, don't worry. Now's a good time to read about what it is. In short, your web app has faster transitions compared to loading entire new pages.
Have multiple routes
Have more than 3 core features
Talk to a backend
Be deployed in production mode
Have all CRUD (Create, Read, Update, Delete) operations for core features
At least two projects should have some concept of user management (signup, login, forgot password, personalization)
At least two projects should use some kind of database or datastore.

Should I showcase variety?

Definitely! Think about it. The aim is to impress someone enough that they hire you, right? Don't build 5 e-commerce apps then. Show that you can do different things

Here are some examples to show variety (pick any 5):

A React app
A vanilla JS app (this will help you in interviews as well)
A React app with offline capabilities i.e. PWA
A Chrome / VS Code / Firefox plugin
A React Native app
A npm package published with tests, docs, and versioning
A REST / GraphQL API

Three Layer Architecture Of web Application in advance JAVA

Presentation Layer
Business Logic Layer
Data access Layer

Another concept-What is three-tier architecture?

Three-tier architecture is a well-established software application architecture that organizes applications into three logical and physical computing tiers: the presentation tier, or user interface; the application tier, where data is processed; and the data tier, where the data associated with the application is stored and managed.

The chief benefit of three-tier architecture is that because each tier runs on its own infrastructure, each tier can be developed simultaneously by a separate development team, and can be updated or scaled as needed without impacting the other tiers.

For decades three-tier architecture was the prevailing architecture for client-server applications. Today, most three-tier applications are targets for modernization, using cloud-native technologies such as containers and microservices, and for migration to the cloud.

The three tiers in detail

Presentation tier

The presentation tier is the user interface and communication layer of the application, where the end user interacts with the application. Its main purpose is to display information to and collect information from the user. This top-level tier can run on a web browser, as desktop application, or a graphical user interface (GUI), for example. Web presentation tiers are usually developed using HTML, CSS and JavaScript. Desktop applications can be written in a variety of languages depending on the platform.

Application tier

The application tier, also known as the logic tier or middle tier, is the heart of the application. In this tier, information collected in the presentation tier is processed - sometimes against other information in the data tier - using business logic, a specific set of business rules. The application tier can also add, delete or modify data in the data tier.

The application tier is typically developed using Python, Java, Perl, PHP or Ruby, and communicates with the data tier using API calls.

Data tier

The data tier, sometimes called database tier, data access tier or back-end, is where the information processed by the application is stored and managed. This can be a relational database management system such as PostgreSQL, MySQL, MariaDB, Oracle, DB2, Informix or Microsoft SQL Server, or in a NoSQL Database server such as Cassandra, CouchDB or MongoDB.

In a three-tier application, all communication goes through the application tier. The presentation tier and the data tier cannot communicate directly with one another.

Tier vs. layer

In discussions of three-tier architecture, layer is often used interchangeably – and mistakenly – for tier, as in 'presentation layer' or 'business logic layer.'

They aren't the same. A 'layer' refers to a functional division of the software, but a 'tier' refers to a functional division of the software that runs on infrastructure separate from the other divisions. The Contacts app on your phone, for example, is a three-layer application, but a single-tier application, because all three layers run on your phone.

The difference is important, because layers can't offer the same benefits as tiers.

Benefits of three-tier architecture

Again, the chief benefit of three-tier architecture its logical and physical separation of functionality. Each tier can run on a separate operating system and server platform - e.g., web server, application server, database server - that best fits its functional requirements. And each tier runs on at least one dedicated server hardware or virtual server, so the services of each tier can be customized and optimized without impact the other tiers.

Other benefits (compared to single- or two-tier architecture) include:

Faster development: Because each tier can be developed simultaneously by different teams, an organization can bring the application to market faster, and programmers can use the latest and best languages and tools for each tier.

Improved scalability: Any tier can be scaled independently of the others as needed.

Improved security: Because the presentation tier and data tier can't communicate directly, a well-designed application tier can function as a sort of internal firewall, preventing SQL injections and other malicious exploits.

Improved reliability: An outage in one tier is less likely to impact the availability or performance of the other tiers.

Three-tier application in web development

In web development, the tiers have different names but perform similar functions:

The web server is the presentation tier and provides the user interface. This is usually a web page or web site, such as an ecommerce site where the user adds products to the shopping cart, adds payment details or creates an account. The content can be static or dynamic, and is usually developed using HTML, CSS and Javascript.

The application server corresponds to the middle tier, housing the business logic used to process user inputs. To continue the ecommerce example, this is the tier that queries the inventory database to return product availability, or adds details to a customer's profile. This layer often developed using Python, Ruby or PHP and runs a framework such as e Django, Rails, Symphony or ASP.NET, for example.

The database server is the data or backend tier of a web application. It runs on database management software, such as MySQL, Oracle, DB2 or PostgreSQL, for example.