What principles should be followed when designing interfaces in java
Nov 23, 2019 am 10:15 AMNormative suggestions for designing java interfaces:
1. Responsibility principle
When designing an interface, the interface must be clear Responsibilities, that is, interface type, what business problems the interface should solve, etc.
2. Principle of Unity
Under the condition of clear interface responsibilities, try to make the interface as single as possible , that is, an interface only does one thing, not two or more. Many non-senior interface designers, when designing interfaces, always think that the more things an interface does, the more awesome it will be. This is a very serious misconception.
3. Protocol specification
When designing the interface, the interface protocol should be clearly defined. Whether to use HTTP protocol, HTTPS protocol or FTP protocol should be determined according to the specific situation.
(1) FTP protocol (File Transfer Protocol, referred to as FTP) is a set of standard file transfer protocols used to transfer files, such as .txt, .csv, etc. For general file transfer, the FTP protocol is used
(2)HTTP protocol, suitable for business scenarios with low or no security requirements
(3)HTTPS=HTTP SSL, suitable for business scenarios with high security requirements
4. Path rules
Since api obtains a resource, try to use nouns in the URL instead of verbs
/api/ v1.0/Pruduct/2019
/api/v1.0/Users/2019
5.http request method
Interface basic access protocol : get (get), post (new), put (modify) and delete (delete)
get /users: List all users
get /users/id: Get based on id User
post /user: New user
put /user/id: Update user based on user id
delete /user/id: Delete based on user id
Recommended tutorial: Getting started with java development
The above is the detailed content of What principles should be followed when designing interfaces in java. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

To correctly handle JDBC transactions, you must first turn off the automatic commit mode, then perform multiple operations, and finally commit or rollback according to the results; 1. Call conn.setAutoCommit(false) to start the transaction; 2. Execute multiple SQL operations, such as INSERT and UPDATE; 3. Call conn.commit() if all operations are successful, and call conn.rollback() if an exception occurs to ensure data consistency; at the same time, try-with-resources should be used to manage resources, properly handle exceptions and close connections to avoid connection leakage; in addition, it is recommended to use connection pools and set save points to achieve partial rollback, and keep transactions as short as possible to improve performance.

Use classes in the java.time package to replace the old Date and Calendar classes; 2. Get the current date and time through LocalDate, LocalDateTime and LocalTime; 3. Create a specific date and time using the of() method; 4. Use the plus/minus method to immutably increase and decrease the time; 5. Use ZonedDateTime and ZoneId to process the time zone; 6. Format and parse date strings through DateTimeFormatter; 7. Use Instant to be compatible with the old date types when necessary; date processing in modern Java should give priority to using java.timeAPI, which provides clear, immutable and linear

Pre-formanceTartuptimeMoryusage, Quarkusandmicronautleadduetocompile-Timeprocessingandgraalvsupport, Withquarkusoftenperforminglightbetterine ServerLess scenarios.2.Thyvelopecosyste,

Java's garbage collection (GC) is a mechanism that automatically manages memory, which reduces the risk of memory leakage by reclaiming unreachable objects. 1.GC judges the accessibility of the object from the root object (such as stack variables, active threads, static fields, etc.), and unreachable objects are marked as garbage. 2. Based on the mark-clearing algorithm, mark all reachable objects and clear unmarked objects. 3. Adopt a generational collection strategy: the new generation (Eden, S0, S1) frequently executes MinorGC; the elderly performs less but takes longer to perform MajorGC; Metaspace stores class metadata. 4. JVM provides a variety of GC devices: SerialGC is suitable for small applications; ParallelGC improves throughput; CMS reduces

Networkportsandfirewallsworktogethertoenablecommunicationwhileensuringsecurity.1.Networkportsarevirtualendpointsnumbered0–65535,withwell-knownportslike80(HTTP),443(HTTPS),22(SSH),and25(SMTP)identifyingspecificservices.2.PortsoperateoverTCP(reliable,c

defer is used to perform specified operations before the function returns, such as cleaning resources; parameters are evaluated immediately when defer, and the functions are executed in the order of last-in-first-out (LIFO); 1. Multiple defers are executed in reverse order of declarations; 2. Commonly used for secure cleaning such as file closing; 3. The named return value can be modified; 4. It will be executed even if panic occurs, suitable for recovery; 5. Avoid abuse of defer in loops to prevent resource leakage; correct use can improve code security and readability.

Gradleisthebetterchoiceformostnewprojectsduetoitssuperiorflexibility,performance,andmoderntoolingsupport.1.Gradle’sGroovy/KotlinDSLismoreconciseandexpressivethanMaven’sverboseXML.2.GradleoutperformsMaveninbuildspeedwithincrementalcompilation,buildcac

The clear answer to this question is the recommendation to implement the observer pattern using a custom observer interface. 1. Although Java provides Observable and Observer, the former is a class and has been deprecated and lacks flexibility; 2. The modern recommended practice is to define a functional Observer interface, and the Subject maintains the Observer list and notify all observers when the state changes; 3. It can be used in combination with Lambda expressions to improve the simplicity and maintainability of the code; 4. For GUI or JavaBean scenarios, PropertyChangeListener can be used. Therefore, new projects should adopt a custom observer interface scheme, which is type-safe, easy to test and specializes in modern Java
