Architectural Components
Base theories from universities worldwide regardless of suggested references:
Mandatory prerequisites for effective Java Architect, besides consultation from universities worldwide upon need based on the needed use cases.
Think about architectural components as lego cubes 🏗 ⚙ whether they're within the same network range (1 system boundary) or between multiple networks (multiple cooperated systems boundaries).
Entity has 1 planned network with 2 sub-networks:
- Internal System for employees [Microsoft technologies plays here].
- External System which externalize services for end users [Sun technologies plays here].
Finally there an integration between those 2 systems to consider an entity is full automated, then there an integration between multiple entities.
Think about Lego cubes 🏗 ⚙ for a sec mate 😇.
To students for playing:
You can draw it on papers using a clean strong papers (A0 size) and pencils with high quality rubbers.
- Proxy
- Load balancer
- RESTful API service:
- Scheduled Job
-
Data storage:
- vertical cylinder
-
Message broker:
- horizontal cylinder
Justification identifies terrorists (thieves) which resides inside the industry worldwide when they try to misuse those components on the cost of human lives without using the theories which get acquired from universities worldwide.
Those terrorists (thieves) are building fucken toys 😨 which are the opposite of all the theories which get taught via universities worldwide that are supported by governments (civilization) worldwide. Which means waste of resources in both human and money level.
Our last hope in our children (👶 => 👨🎓 and 👩🎓) in the future, maybe 100 years later or so, when those ignorant fagot licentious thieves terrorists got vanished 🤜 🕳 via security authorities (UN elite special forces 🦇 [BLACK-OPS]) worldwide.
Do not use horizontal-scaling in testing environment. Just 1 replica is enough which means saving some money like power consumption (electricity bills) and others not on the cost of human lives as those fagot licentious thieves terrorists (thieves) in the industry do. We postpone this step till production environment for high availability and stability and others 💪. Replication is used on REST-API-service level to maximize the usage of http-thread-pool per component that are responsible to serve the requests of users to avoid being on-hold in-front-of the http-thread-pool.
-
Vertical-Scaling for those components should be planned first, because there is a difference between testing and production environments, also be aware that
production environmentshall be constructed upon finishing the development of the required software and verifying it via the Testers (QA Stuff). -
At this moment the successful developed verified software shall be
replicatedfromtesting environmentto the newly constructedproduction environment, then the Testers (QA Stuff) have to do a regression test roundticket by ticketto double check its usability and stability before declaring the end of the project and close the deal, then the final end users will be ready to use the service.
Timing ✊ matters to reduce the bills based on science which get acquired from universities worldwide not as those fagot licentious thieves terrorists (thieves) in the industry do on the cost of the human lives.
Please visit this link for jokes 🤣 to avoid being a naive.
When you become a bloody-hell-authentic-strong-architect 💪 😇, then you can depend on this tool to start initiating the services properly without wasting a lot of time on manual-work.
