Tag: was

WEB SERVICE 3-TIERS

Posted on by lechuck park

From Claude with some prompting
WEB(Front) Layer

  • Primary Components:
    • Static Data: HTML, CSS, JavaScript files
    • Storage: Browser-based storage solutions
  • Performance Optimization:
    • CDN: Global content delivery
    • Caching: Response time improvement
  • Enhanced Custom Experience:
    • Optimized user interface
    • Client-side performance enhancements
  1. WAS(Back) Layer
  • Core Functions:
    • Program Code: Server-side application logic
    • Computing: Business process handling
  • Development Features:
    • Enhanced Development Environment (CI/CD):
      • Continuous Integration for automated testing
      • Continuous Deployment for automated delivery
      • Automated build and release processes
      • Development workflow optimization
    • Biz Logic: Business rules implementation
    • Microservices: Modular service architecture
  1. DB Layer
  • Data Management:
    • Dynamic Data: Real-time data processing
    • Variable(Memory): Memory-based data handling
  • Business Data:
    • Biz Data Scheme & ACID:
      • Data structure and relationships
      • Transaction integrity
      • Data consistency
    • RDBMS/NoSQL: Flexible database solutions
  1. Infrastructure Characteristics
  • High Availability (Biz Continues):
    • Uninterrupted service operation
    • Fault tolerance
    • Business continuity
  • Scalability (Biz Changes):
    • System expansion capability
    • Business growth support
    • Flexible architecture
  1. Key Integration Points
  • WEB ↔ WAS: Static data and program code interaction
  • WAS ↔ DB: Dynamic data and business logic connection
  • Biz Logic ↔ Biz Data: Direct business data operations

This architecture demonstrates a modern, well-structured web service that emphasizes:

Robust business logic handling
Efficient data management
Clear separation of concerns
Automated development processes
Scalable infrastructure
High availability
Enhanced user experience

HTTP Service components

Posted on by lechuck park

From Claude with some prompting
This image illustrates the network structure of an HTTP service. The main components are:

Client Side:

  • Browser: Handles URL requests, HTML parsing, and JavaScript execution
  • OS: Runs the browser, translates URL (domain) to IP

Internet:

  • DNS: Converts domain names to IP addresses
  • IP: Transfers data using IP addresses

Server Side:

  • OS (Operating System): Runs applications, manages IP network
  • TLS: Handles encryption
  • WEB:
    • Manages HTML embedding
    • Handles JSP (JavaServer Pages)
    • Typically deals with static content and some dynamic content generation
  • WAS (Web Application Server):
    • Handles server-side programming and application logic
    • Manages complex dynamic content generation
    • Interacts with the database
    • Handles business logic of the application
  • DB: Database for storing and retrieving data for web services

The diagram shows the entire process of how an HTTP request is handled, from the web browser to the server’s database. It briefly explains the technologies and protocols involved at each step, providing a helpful overview of the basic structure of web services.