Java Hyd Team pinned «Cglia solutions LLp Road no: 27 jubilee hills Near MCR hrd inst Hyderabad 500 033»
Java Hyd Team pinned «ACT Fibernet Atria Convergence Technologies https://maps.app.goo.gl/Jc2LBbkxTw4hXkVS8»
Can array store objects (heterogeneous type parameters)
Anonymous Poll
61%
Yes (object [] a = new object[100]; a[0] = new student (); a[1] = new employee ();
39%
No , the above mentioned is wrong
👍2😁2
👍3
What is the Root interface of collection framework
Anonymous Poll
58%
Collection
37%
Utility
5%
Lang
Which interface in collection contains most used / common methods in framework
Anonymous Poll
58%
Collection
8%
Lang
33%
Util
8%
Contains
Which class can't implement collection interfaces
Anonymous Poll
47%
Singleton
24%
Concrete
0%
Normal
6%
Public Class
12%
Private class
12%
Protected class
Difference between collection and collections
Anonymous Poll
46%
Collection is interface & Collections is a class
62%
collection represent group of individual objects as a single entity & Collections is an Utility clas
👍1
People in this group don't have basics 😒😒 when we plan something for you guy's you all are super busy in this planet whatever we do for you all is not worthy for you providing hand written notes or videos will not be worthy till the time you will not practice the concepts don't just use loop or conditions even if you write wrong code it's okay just do wrong code but do
Whatever we share is for you guy's only if you just be here with us 100% for a year definitely will be in good product base companies and with good package 📦 📦
Code First v.s. API First - A change of software development philosophy.
The diagram below shows the differences between code-first development and API-first development. Why do we want to consider API first design?
🔹 Microservices increase system complexity
We have separate services to serve different functions of the system. While this kind of architecture facilitates decoupling and segregation of duty, we need to handle the various communications among services.
It is better to think through the system's complexity before writing the code and carefully defining the boundaries of the services.
🔹 Separate functional teams need to speak the same language
The dedicated functional teams are only responsible for their own components and services. It is recommended that the organization speak the same language via API design.
We can mock requests and responses to validate the API design before writing code.
🔹 Improve software quality and developer productivity
Since we have ironed out most of the uncertainties when the project starts, the overall development process is smoother, and the software quality is greatly improved.
Developers are happy about the process as well because they can focus on functional development instead of negotiating sudden changes.
The possibility of having surprises toward the end of the project lifecycle is reduced.
Because we have designed the API first, the tests can be designed while the code is being developed. In a way, we also have TDD (Test Driven Design) when using API first development.
👉 Over to you: Do you use code-first or API-first development in your work?
The diagram below shows the differences between code-first development and API-first development. Why do we want to consider API first design?
🔹 Microservices increase system complexity
We have separate services to serve different functions of the system. While this kind of architecture facilitates decoupling and segregation of duty, we need to handle the various communications among services.
It is better to think through the system's complexity before writing the code and carefully defining the boundaries of the services.
🔹 Separate functional teams need to speak the same language
The dedicated functional teams are only responsible for their own components and services. It is recommended that the organization speak the same language via API design.
We can mock requests and responses to validate the API design before writing code.
🔹 Improve software quality and developer productivity
Since we have ironed out most of the uncertainties when the project starts, the overall development process is smoother, and the software quality is greatly improved.
Developers are happy about the process as well because they can focus on functional development instead of negotiating sudden changes.
The possibility of having surprises toward the end of the project lifecycle is reduced.
Because we have designed the API first, the tests can be designed while the code is being developed. In a way, we also have TDD (Test Driven Design) when using API first development.
👉 Over to you: Do you use code-first or API-first development in your work?