<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Geethika Shalani on Medium]]></title>
        <description><![CDATA[Stories by Geethika Shalani on Medium]]></description>
        <link>https://medium.com/@gethikashalani?source=rss-28d9a1d6ceeb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ezDhusp1BKH6pCUg</url>
            <title>Stories by Geethika Shalani on Medium</title>
            <link>https://medium.com/@gethikashalani?source=rss-28d9a1d6ceeb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:41:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gethikashalani/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Virtualization types.]]></title>
            <link>https://medium.com/@gethikashalani/virtualization-types-cbaa228f3423?source=rss-28d9a1d6ceeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbaa228f3423</guid>
            <dc:creator><![CDATA[Geethika Shalani]]></dc:creator>
            <pubDate>Sat, 21 Oct 2023 05:40:25 GMT</pubDate>
            <atom:updated>2023-10-21T05:49:54.310Z</atom:updated>
            <content:encoded><![CDATA[<p>Virtualization is a technology that allows you to create and run multiple virtual instances of computers or operating systems on a single physical machine. Virtualization has become a fundamental technology in modern data centers and cloud computing, enabling efficient resource utilization, scalability, and flexibility. It is widely used for server consolidation, cloud services, and development and testing environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*who5Ra6DQccHtF5Z9ZjOpg.png" /></figure><h4><strong>Desktop Virtualization:</strong></h4><p>Desktop virtualization, often referred to as Virtual Desktop Infrastructure (VDI), is a technology that virtualizes desktop computing environments. It enables multiple virtual desktops to run on a single physical machine, providing a more efficient and flexible way to manage and deliver desktop computing services. Desktop virtualization offers several advantages, making it a popular choice in various business and IT environments.</p><p>Use Cases:</p><ul><li>Remote Work: Desktop virtualization is valuable for remote work scenarios, as users can access their work environments from anywhere with an internet connection.</li><li>Software Testing and Development: Virtual desktops can be easily cloned and configured for software development and testing.</li><li>BYOD (Bring Your Own Device): It allows employees to use their personal devices for work while maintaining security and control over corporate data.</li><li>Legacy Application Support: Legacy applications that are not compatible with modern operating systems can be run in virtual desktops.</li></ul><p>Types of Desktop Virtualization:</p><ul><li>Hosted VDI: In hosted VDI, virtual desktops run on servers in a data center or cloud. Users access their virtual desktops via a remote connection, typically using a client application or a web browser.</li><li>Client VDI: In client VDI, virtual desktops run on the user’s device, but they are still centrally managed and controlled by the IT department. This approach can be used for offline or remote access.</li><li>Remote Desktop Services (RDS): RDS is a form of desktop virtualization where multiple users share a single instance of a server operating system. Users access their desktop environments remotely through the RDS protocol.</li></ul><p>Benefits:</p><ul><li>Centralized Management: IT administrators can manage and maintain desktops from a centralized location. This simplifies tasks such as software updates, security patches, and configuration changes.</li><li>Security: Data and applications are stored centrally, reducing the risk of data loss or theft on individual devices. Virtual desktops can be easily backed up and secured in the data center.</li><li>Cost Savings: By consolidating desktops on server hardware, organizations can reduce the number of physical PCs needed and save on hardware costs, energy consumption, and support expenses.</li><li>Flexibility: Users can access their virtual desktops from various devices, including thin clients, laptops, tablets, or even smartphones. This offers flexibility in where and how work is performed.</li><li>Scalability: It’s easier to scale desktop environments up or down as needed, making it simple to add or remove virtual desktops to accommodate changing workloads.</li></ul><p>Challenges:</p><ul><li>Infrastructure Costs: Setting up and maintaining a virtual desktop infrastructure can be expensive, especially in terms of server hardware and storage.</li><li>Network Dependency: Network performance is critical for a good user experience, and a slow or unreliable network connection can lead to usability issues.</li><li>Licensing and Software Costs: Software licensing for VDI solutions and virtual desktop operating systems can add to the overall cost.</li></ul><h4><strong>Application Virtualization:</strong></h4><p>Application virtualization is a technology that isolates and encapsulates individual software applications from the underlying operating system and hardware, allowing these applications to run in a controlled, sandboxed environment. This approach is designed to improve application management, compatibility, and security.</p><p>Use Cases:</p><ul><li>Legacy Application Support: Organizations can continue to use critical legacy applications on modern operating systems without compatibility issues.</li><li>Testing and Development: Application virtualization allows developers to create isolated environments for testing and development, ensuring that changes made during development do not disrupt other applications or the host system.</li><li>Security: Virtualizing sensitive applications can provide an additional layer of security by isolating them from other parts of the system.</li></ul><p>Benefits:</p><ul><li>Application Compatibility: It allows older or incompatible applications to run on newer operating systems, as they can operate in an environment tailored to their specific requirements.</li><li>Conflict Resolution: Applications with conflicting dependencies or settings can coexist peacefully in isolated environments.</li><li>Security: The isolated nature of virtualized applications can enhance security by reducing the potential attack surface. Malware or malicious code within a virtualized application is less likely to affect the entire system.</li><li>Portability: Virtualized applications can be packaged and run on various systems without extensive installation, making them portable and easy to distribute.</li><li>Streamlining Updates: Applications can be updated independently from the underlying OS, simplifying software maintenance.</li></ul><p>How Application Virtualization Works:</p><ul><li>Packaging: The application and its associated files, settings, and dependencies are packaged into a virtualized container. This container can be a single file that contains everything needed to run the application.</li><li>Runtime Environment: When the virtualized application is executed, it runs within an isolated runtime environment that simulates the required components of an operating system, such as file systems and registries.</li><li>Registry and File System Redirection: The virtualization technology redirects file system and registry calls made by the virtualized application to the isolated environment, ensuring that the application’s changes don’t affect the host system.</li></ul><p>Challenges:</p><ul><li>Resource Overhead: Application virtualization may introduce some performance overhead due to the isolation and redirection processes.</li><li>Licensing: Application virtualization solutions often require their own licensing, which can add to the overall cost.</li><li>Complexity: Managing a large number of virtualized applications can be complex and require proper organization and maintenance.</li></ul><h4><strong>Network Virtualization:</strong></h4><p>Network virtualization is a technology that abstracts and virtualizes the physical network infrastructure, allowing the creation of multiple virtual network segments or overlays on top of a shared physical network. It enables the segmentation and isolation of network traffic for different purposes, enhancing network flexibility, scalability, and management.</p><p>Use Cases:</p><ul><li>Data Center Virtualization: Network virtualization is widely used in data centers to segment traffic, enhance resource utilization, and simplify network management.</li><li>Cloud Computing: Virtual networks in cloud environments allow providers to isolate customer traffic, ensuring security and network privacy.</li><li>Multi-Tenancy: Service providers use network virtualization to provide isolated network segments to multiple customers or tenants.</li></ul><p>Types of Network Virtualization:</p><ul><li>Overlay Virtualization: Overlay network virtualization encapsulates packets within other packets, creating virtual networks that are independent of the underlying physical network. Technologies like VXLAN and NVGRE are commonly used for overlay virtualization.</li><li>Software-Defined Networking (SDN): SDN is a network virtualization approach that centralizes network control, separating it from the data plane. It allows network administrators to manage network traffic and routing through software, enhancing flexibility and agility.</li><li>Network Function Virtualization (NFV): NFV virtualizes network services like firewalls, load balancers, and routers, allowing them to run as virtual machines or containers on standard hardware. It reduces the need for dedicated, proprietary hardware and simplifies network service management.</li></ul><p>Benefits:</p><ul><li>Isolation: Virtual networks are isolated from each other, ensuring that network traffic on one virtual network does not interfere with another.</li><li>Efficiency: Network resources are more efficiently utilized as multiple virtual networks share the same physical infrastructure.</li><li>Security: Isolation enhances security by preventing unauthorized access and reducing the potential attack surface.</li><li>Scalability: It simplifies the process of adding or modifying network resources, enabling rapid scaling to accommodate changing workloads.</li><li>Flexibility: Network configurations can be easily adapted to meet the specific needs of different applications or services.</li></ul><p>Challenges:</p><ul><li>Complexity: Network virtualization can introduce complexity, particularly in large, multi-tenant environments.</li><li>Performance: Overlay virtualization may introduce additional overhead due to encapsulation and decapsulation of packets.</li><li>Security: While network virtualization can enhance security, it also introduces new challenges, such as ensuring the security of the virtualization infrastructure itself.</li></ul><h4><strong>Storage Virtualization:</strong></h4><p>Storage virtualization is a technology that abstracts and virtualizes physical storage resources to create a more flexible, efficient, and scalable storage infrastructure. It allows multiple physical storage devices to be pooled together and presented as a single, logical storage resource. Storage virtualization provides several advantages, such as improved management, scalability, and data availability.</p><p>Use Cases:</p><ul><li>Data Center Storage: Storage virtualization is commonly used in data centers to aggregate storage resources, improve management, and enhance data availability.</li><li>Storage Consolidation: Organizations use storage virtualization to consolidate multiple storage systems into a single, more efficient storage infrastructure.</li><li>Disaster Recovery: Virtualized storage simplifies the replication and migration of data for disaster recovery purposes.</li><li>Multi-Tenancy: In multi-tenant environments, storage virtualization helps allocate and manage storage resources for different tenants.</li></ul><p>Types of Storage Virtualization:</p><ul><li>File-Level Virtualization: This type of storage virtualization abstracts individual files, allowing them to be stored across different physical storage systems. It simplifies data management and provides a global namespace for files.</li><li>Block-Level Virtualization: Block-level virtualization abstracts and virtualizes storage at the disk block level. It provides better performance and flexibility but typically requires more complex management.</li><li>Object Storage Virtualization: Object storage virtualization abstracts object storage resources and enables the storage of large volumes of unstructured data, such as multimedia files, in a scalable manner.</li></ul><p>Benefits:</p><ul><li>Aggregation: Multiple storage devices, including different types and brands, can be aggregated into a unified storage pool, which is easier to manage and more efficient.</li><li>Efficiency: Storage resources are used more effectively, reducing wasted capacity and improving performance.</li><li>Flexibility: Virtualized storage can be easily resized and allocated to applications as needed, allowing for better scalability.</li><li>Data Migration: Data can be seamlessly moved between different storage devices without disrupting access to the data, enhancing data mobility and availability.</li><li>Data Protection: Many storage virtualization solutions provide features like data replication, snapshotting, and backup integration, which improve data protection and disaster recovery capabilities.</li></ul><p>Challenges:</p><ul><li>Complexity: Implementing and managing storage virtualization solutions can be complex, especially in large environments.</li><li>Performance: Some storage virtualization solutions may introduce performance overhead due to the additional layer of abstraction.</li><li>Cost: While storage virtualization can provide cost savings through better resource utilization, there are initial costs associated with implementing the technology.</li></ul><h4><strong>Server Virtualization:</strong></h4><p>Server virtualization is a technology that enables multiple virtual servers or virtual machines (VMs) to run on a single physical server, effectively abstracting and separating the physical hardware from the operating systems and applications running on it. This approach allows for efficient resource utilization, improved scalability, flexibility, and simplified server management.</p><p>Use Cases:</p><ul><li>Server Consolidation: Server virtualization is often used to consolidate multiple physical servers onto a smaller number of physical hosts.</li><li>Data Center Virtualization: It is a core technology in modern data centers, enabling efficient resource utilization, scaling, and agility.</li><li>Cloud Computing: Cloud providers use server virtualization to allocate virtual machines to customers on shared physical infrastructure.</li><li>Legacy Application Support: Virtualization allows legacy applications designed for older hardware and operating systems to continue running on modern servers.</li></ul><p>Benefits:</p><ul><li>Resource Utilization: Multiple virtual machines can run on a single physical server, maximizing the use of CPU, memory, storage, and network resources.</li><li>Isolation: Each virtual machine operates independently of the others, ensuring that issues with one VM do not affect the others.</li><li>Consolidation: Server virtualization allows organizations to consolidate their physical server infrastructure, reducing hardware costs and data center space requirements.</li><li>Flexibility: Virtual machines can be easily created, cloned, and resized, making it straightforward to adapt to changing workloads and resource requirements.</li><li>Disaster Recovery: Virtual machines can be backed up and migrated to other physical servers, simplifying disaster recovery and business continuity planning.</li><li>Testing and Development: Developers can create and test virtual machine instances with different configurations without the need for dedicated hardware.</li></ul><p>Challenges:</p><ul><li>Resource Contention: When multiple virtual machines share the same physical server, resource contention can occur, impacting performance.</li><li>Overhead: Hypervisor-based virtualization may introduce some performance overhead due to the virtualization layer.</li><li>Licensing and Costs: Licensing costs for hypervisor software and additional hardware resources should be considered.</li></ul><h4><strong>Data virtualization:</strong></h4><p>Data virtualization is a technology that abstracts and presents data from various sources, including databases, cloud storage, and other data repositories, as a single, unified data source. It provides a logical layer that allows users and applications to access and query data without needing to know the physical location or structure of the underlying data. Data virtualization offers several benefits, including improved data access, integration, and agility.</p><p>Use Cases:</p><ul><li>Data Integration: Data virtualization simplifies data integration efforts by connecting to and consolidating data from multiple sources.</li><li>Business Intelligence and Analytics: It provides a unified view of data for analytics and reporting, enabling more informed decision-making.</li><li>Data Federation: Data virtualization can be used to create a virtual data warehouse that federates data from various sources.</li><li>Legacy Data Access: Organizations can access and utilize data from legacy systems without migrating the data to modern storage solutions.</li></ul><p>Benefits:</p><ul><li>Simplified Data Access: Data virtualization simplifies data access by providing a unified interface for querying and retrieving data from various sources.</li><li>Data Integration: It allows data from diverse sources to be integrated and presented as a single, coherent dataset, reducing the need for complex ETL (Extract, Transform, Load) processes.</li><li>Real-Time Data Access: Data virtualization can provide real-time or near-real-time access to data, ensuring that users have access to the most up-to-date information.</li><li>Data Agility: Organizations can quickly adapt to changing data needs, add new data sources, and make changes to data models without disrupting existing processes.</li><li>Cost Reduction: By eliminating the need to physically consolidate data into a single repository, data virtualization can reduce storage and maintenance costs.</li></ul><p>How Data Virtualization Works:</p><ul><li>Data Source Connectivity: Data virtualization platforms connect to a variety of data sources, including databases, APIs, cloud storage, and data warehouses.</li><li>Data Modeling and Abstraction: Data is modeled and abstracted into a common format and structure, making it accessible through a unified interface.</li><li>Query Optimization: Data virtualization platforms can optimize queries to fetch only the necessary data, improving performance.</li><li>Security and Governance: Data virtualization solutions often include security and governance features to ensure data access is controlled and compliant with regulations.</li></ul><p>Challenges:</p><ul><li>Performance: While data virtualization can provide real-time access to data, performance may be a concern for extremely large datasets or complex queries.</li><li>Data Governance: Ensuring data security and governance in a virtualized environment can be challenging, particularly in multi-tenant setups.</li><li>Data Source Compatibility: Data virtualization platforms must be compatible with various data sources, which can be complex to manage.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbaa228f3423" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Distributed System Architecture.]]></title>
            <link>https://medium.com/@gethikashalani/distributed-system-architecture-90eb45da123a?source=rss-28d9a1d6ceeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/90eb45da123a</guid>
            <dc:creator><![CDATA[Geethika Shalani]]></dc:creator>
            <pubDate>Sat, 14 Oct 2023 16:18:43 GMT</pubDate>
            <atom:updated>2023-10-20T14:03:35.230Z</atom:updated>
            <content:encoded><![CDATA[<p>A distributed system architecture refers to the design and organization of a computer system that consists of multiple interconnected, autonomous devices or components that work together to achieve a common goal. In a distributed system, these devices can be located in different physical locations and can communicate with each other over a network. This architecture is often used to improve scalability, fault tolerance, and performance in large and complex computing environments. Here are some key aspects and components of a distributed system architecture:</p><h4><strong>Nodes/Components:</strong></h4><p>In a distributed system architecture, nodes or components are the individual entities or devices that make up the system. These nodes work together to provide various services and functionalities in a coordinated manner. The specific types of nodes or components in a distributed system can vary depending on the architecture and the requirements of the system, but here are some common types:</p><ol><li>Client Nodes: These are typically end-user devices or applications that interact with the distributed system.</li><li>Server Nodes: Server nodes are responsible for processing client requests, executing application logic, and managing data.</li><li>Middleware Nodes: Middleware nodes provide services that help facilitate communication and coordination between other nodes.</li><li>Load Balancers: Load balancers distribute incoming client requests across multiple server nodes to ensure even workload distribution and improve system performance.</li><li>Caching Servers: Caching nodes store frequently accessed data or results to reduce the load on the backend servers and improve response times.</li><li>Proxy Servers: Proxy nodes act as intermediaries between clients and servers. They can provide security and content filtering, as well as serve as caching points to optimize content delivery.</li><li>Message Brokers: Message broker nodes facilitate asynchronous communication between components in a distributed system.</li><li>Replication Servers: Replication nodes replicate data or services across multiple nodes to improve data availability and fault tolerance.</li><li>Coordinator Nodes: Coordinator nodes are responsible for managing distributed transactions and ensuring that multiple operations across different nodes are atomic and consistent.</li><li>Naming and Directory Services: These nodes provide naming and directory services, allowing other components to locate resources and services in the distributed system.</li><li>Gateway Nodes: Gateway nodes bridge the gap between different network protocols or communication technologies, allowing components with different communication methods to interact.</li><li>Security Nodes: Security nodes handle authentication, authorization, encryption, and other security-related functions to protect the integrity and privacy of data in the distributed system.</li></ol><h4><strong>Communication:</strong></h4><p>Communication is a fundamental aspect of distributed systems, as it enables nodes within the system to exchange data and coordinate their actions. Effective communication is essential for ensuring that a distributed system operates correctly and efficiently. There are several key aspects to consider when it comes to communication in distributed systems:</p><ol><li>Message Passing: Message passing is a common communication method in distributed systems. Nodes send messages to each other to request services, exchange data, or notify about events.</li><li>Remote Procedure Calls (RPC): RPC is a mechanism that allows a program to execute procedures or functions on a remote node as if they were local.</li><li>Message Queues: Message queues are used to implement asynchronous communication patterns in which messages are placed in a queue and processed by consumers at their own pace.</li><li>Publish-Subscribe: The publish-subscribe pattern allows nodes to publish events or messages, and other nodes can subscribe to specific events of interest.</li><li>Sockets and Networking: Low-level network sockets enable direct communication between nodes in a distributed system. Protocols like TCP and UDP are commonly used for socket-based communication.</li><li>RESTful APIs: Representational State Transfer (REST) is an architectural style that uses HTTP for communication.</li><li>WebSockets: WebSockets provide a full-duplex, bidirectional communication channel over a single TCP connection. They are used for real-time and interactive applications, such as online chat and gaming.</li><li>Serialization: Data exchanged between nodes needs to be serialized (converted to a format that can be transmitted) and deserialized (converted back into a usable form).</li><li>Data Formats: Distributed systems often need to agree on common data formats and schemas for the messages they exchange.</li><li>Security: Communication in a distributed system must be secure. Techniques such as encryption (e.g., TLS/SSL), digital signatures, and authentication mechanisms are used to protect data in transit.</li><li>Load Balancing: Load balancers distribute incoming requests across multiple server nodes to ensure even workload distribution.</li><li>Error Handling and Retry: Distributed systems must handle communication failures and retries gracefully.</li><li>Monitoring and Logging: Effective communication often involves monitoring the system’s communication patterns and logging relevant information for troubleshooting and debugging.</li><li>Quality of Service (QoS): Some distributed systems require specific guarantees on communication quality, such as low latency, high bandwidth, or reliability.</li><li>Message Routing and Routing Tables: In complex distributed systems, routing tables and algorithms are used to determine how messages should be forwarded to the appropriate destination nodes.</li></ol><h4><strong>Middleware:</strong></h4><p>Middleware is a crucial component in distributed systems that provides a layer of software between the operating system and application software, facilitating communication and interaction between different components and nodes within the system. Middleware acts as an intermediary layer that abstracts the complexities of distributed computing, making it easier to develop, deploy, and manage distributed applications. Here are key aspects and functions of middleware in distributed systems:</p><ol><li>Communication Abstraction: Middleware abstracts the details of low-level network communication and provides a higher-level, more developer-friendly interface for communication between distributed components.</li><li>Message Passing: Middleware often includes messaging systems that enable asynchronous message passing between nodes in the distributed system.</li><li>Remote Procedure Calls (RPC): Middleware can facilitate RPC, allowing components to invoke methods or functions on remote nodes as if they were local.</li><li>Publish-Subscribe: Middleware may provide publish-subscribe mechanisms, allowing components to publish events or messages and subscribe to specific topics or events of interest.</li><li>Data Transformation and Serialization: Middleware can handle data transformation and serialization to ensure that data exchanged between components is in a compatible format, which is especially important when communicating between systems with different data representations.</li><li>Security: Middleware often includes security features for authentication, authorization, and encryption to protect data and communications in the distributed system.</li><li>Load Balancing: Some middleware components may include load balancing capabilities to evenly distribute incoming requests or messages across multiple servers or nodes for better performance and fault tolerance.</li><li>Transaction Management: Middleware can provide support for distributed transactions, ensuring that multiple operations on different nodes are executed atomically and consistently.</li><li>Naming and Directory Services: Middleware can offer naming and directory services, allowing components to locate resources, services, or other components in the distributed system using a naming or addressing mechanism.</li><li>Concurrency and Synchronization: Middleware may provide tools and libraries for managing concurrency and synchronization in distributed systems, helping to avoid data conflicts and race conditions.</li><li>Monitoring and Management: Middleware often includes tools for monitoring the health and performance of the distributed system and provides mechanisms for managing and configuring system components.</li><li>Message Queues: Middleware can include message queuing systems that allow asynchronous communication, message storage, and reliable message delivery, which is essential for scenarios where messages need to be processed in a decoupled manner.</li><li>Event Handling: Middleware can handle event-driven programming, allowing components to react to and process events generated by other components.</li><li>Scalability: Middleware may offer features for horizontal scalability by allowing the dynamic addition of new nodes or components to handle increased workloads.</li><li>Integration with Legacy Systems: Middleware can bridge the gap between modern distributed systems and legacy systems, enabling communication and data exchange with older, non-distributed systems.</li></ol><h4><strong>Scalability:</strong></h4><p>Scalability is a fundamental concept in distributed systems and software architecture that refers to a system’s ability to handle increased workloads by efficiently adding more resources or nodes without compromising performance or responsiveness. Scalability is crucial for ensuring that a system can grow to meet the demands of its users and data processing requirements. There are generally two types of scalability:</p><ol><li>Vertical Scalability (Scaling Up).</li><li>Horizontal Scalability (Scaling Out).</li></ol><p>Key considerations and strategies for achieving scalability in distributed systems include:</p><ol><li>Load Balancing: Load balancers can intelligently route requests to the least loaded nodes.</li><li>Statelessness: Designing components to be stateless, meaning they do not rely on the state of a particular server or session.</li><li>Data Partitioning: Distributing data across multiple nodes or databases to avoid data bottlenecks.</li><li>Caching: Using caching mechanisms to store frequently accessed data or results at the edge of the system to reduce the load on backend servers and improve response times.</li><li>Replication: Replicating data or services across multiple nodes to ensure high availability and fault tolerance.</li><li>Microservices: Adopting a microservices architecture, where different components or services are designed as independently deployable units.</li><li>Elasticity: Building systems that can dynamically adapt to changes in workloads by automatically adding or removing nodes as needed.</li><li>Distributed Databases: Using distributed database systems that allow data to be distributed and replicated across multiple nodes for efficient data access and fault tolerance.</li><li>Stateful and Stateless Components: Identifying which components of the system can be stateless and which require state, and optimizing the architecture accordingly.</li><li>Monitoring and Performance Testing: Continuously monitoring the system’s performance and conducting load tests to identify bottlenecks and scalability issues.</li><li>Scalable Communication: Ensuring that communication between nodes is efficient and scalable. This may involve optimizing message passing, using message queues, and adopting asynchronous communication patterns.</li></ol><h4><strong>Load balancing:</strong></h4><p>Load balancing is a critical component in distributed systems and network architectures that involves distributing incoming network traffic or workloads across multiple nodes or servers. The primary goal of load balancing is to ensure that no single node is overwhelmed with too much traffic, thus optimizing system performance, improving fault tolerance, and ensuring a better user experience. Here are the key aspects and strategies related to load balancing:</p><ol><li>Even Workload Distribution: The central purpose of load balancing is to distribute incoming requests or tasks evenly across multiple nodes.</li><li>High Availability: Load balancers can be configured to route traffic only to healthy nodes.</li><li>Improved Performance: Load balancing can lead to improved system performance by efficiently utilizing the available resources.</li><li>Scalability: Load balancers support horizontal scalability. When the traffic load increases, you can easily add more nodes to the system, and the load balancer will distribute traffic accordingly.</li><li>Health Checks: Load balancers typically perform health checks on nodes to assess their status. If a node fails a health check, the load balancer can stop routing traffic to that node until it recovers.</li><li>Session Persistence: While statelessness is often encouraged in distributed systems, certain applications require session persistence, where a user’s requests are consistently directed to the same server.</li><li>Load Balancing Algorithms: Load balancers use various algorithms to determine how to distribute traffic.</li><li>Content-Based Routing: In more advanced scenarios, content-based routing is used, where the load balancer examines the content or attributes of the request to determine which node should handle it.</li><li>Global Load Balancing: In geographically distributed systems, global load balancers route traffic to the nearest data center or server location to reduce latency and optimize performance.</li><li>Hardware and Software Load Balancers: Hardware load balancers are dedicated devices optimized for high-performance load balancing, while software load balancers are often deployed on commodity hardware or in virtualized environments.</li><li>CDNs (Content Delivery Networks): Content delivery networks use load balancing as a fundamental component to optimize content delivery by routing user requests to the nearest and most suitable server, improving response times and reducing network latency.</li><li>Auto-Scaling: In cloud environments, auto-scaling can be combined with load balancing to automatically add or remove instances based on resource usage, ensuring that the system can adapt to varying workloads.</li><li>Logging and Monitoring: Load balancers provide logging and monitoring capabilities, allowing administrators to track the performance of nodes, detect issues, and troubleshoot load balancing configurations.</li></ol><h4><strong>Fault tolerance:</strong></h4><p>Fault tolerance is a critical concept in distributed systems and computing that refers to a system’s ability to continue functioning and providing services in the presence of faults, errors, or failures. Faults can occur due to hardware failures, software bugs, network issues, or other unforeseen circumstances. The goal of building fault-tolerant systems is to ensure system availability, reliability, and resilience. Here are key aspects and strategies related to fault tolerance:</p><ol><li>Redundancy: Redundancy involves replicating critical components, services, or data to ensure that a backup is available in case the primary component fails. Common forms of redundancy include:</li><li>Automatic Failover: Automatic failover reduces downtime and ensures continuous service availability.</li><li>Monitoring and Health Checks: Implementing robust monitoring and health-check mechanisms to continuously assess the health and performance of system components.</li><li>Load Balancing: Load balancers play a role in fault tolerance by distributing traffic across multiple nodes.</li><li>Graceful Degradation: This means that even if some components fail, the system can continue to provide basic functionality while certain non-critical features may be temporarily unavailable.</li><li>Data Backup and Recovery: Regularly backing up data and implementing data recovery mechanisms in case of data corruption or loss.</li><li>Replication: Replicating data or services across multiple nodes to ensure high availability.</li><li>Statelessness: Statelessness simplifies failover because requests can be redirected to any available node.</li><li>Quorum Systems: Using quorum systems and consensus algorithms to make decisions in distributed systems.</li><li>Isolation of Faults: Isolating faults to prevent them from affecting other parts of the system.</li><li>Geographic Distribution: Geographically distributing components across different data centers or regions to mitigate the impact of localized disasters or network issues.</li><li>Stateful Service Recovery: In some cases, stateful services may require mechanisms to recover their state after a failure, such as through replication and checkpointing.</li><li>Testing and Simulation: Extensive testing and simulation of failure scenarios to validate that the system can withstand various faults.</li><li>Documentation and Recovery Plans: Maintaining documentation and recovery plans that outline how to respond to various types of failures, including recovery procedures and the roles of administrators.</li><li>Fail-Safe Defaults: Setting system defaults to a fail-safe state when an unexpected fault occurs, ensuring that the system takes a safe course of action.</li></ol><h4><strong>Consistency and replication:</strong></h4><p>Consistency and replication are critical concepts in distributed systems, particularly when dealing with distributed databases or data storage systems. They address the challenges of ensuring data accuracy, availability, and reliability across multiple nodes or replicas in a distributed environment. Here’s a closer look at consistency and replication:</p><p>Consistency:</p><ul><li>Strong Consistency: Strong consistency provides the highest level of data consistency but may come at the cost of higher latency and reduced availability in the event of network partitions or failures.</li><li>Eventual Consistency: Eventual consistency allows for temporary inconsistencies between replicas, but guarantees that, given enough time and no further updates, all replicas will eventually converge to the same data.</li><li>Causal Consistency: This approach provides a balance between strong and eventual consistency, allowing for more flexible and efficient systems while preserving causality.</li></ul><p>Replication:</p><ul><li>Active Replication: In active replication, all replicas actively process requests and updates. This approach can provide high availability but requires mechanisms for consistency, like quorum systems or consensus algorithms.</li><li>Passive Replication: Passive replication involves one primary replica actively processing updates, while secondary replicas passively follow the primary’s state. Passive replication is often used for fault tolerance and load balancing.</li></ul><h4><strong>Security:</strong></h4><p>Security is a critical consideration in distributed systems and, indeed, in all aspects of computing and information technology. In a distributed system, security measures are necessary to protect data, resources, and communication between nodes. Here are some key aspects of security in distributed systems:</p><ol><li>Authentication: Authentication is the process of verifying the identity of users, nodes, or entities in a distributed system. Common authentication mechanisms include username-password pairs, biometrics, and cryptographic certificates.</li><li>Authorization: Authorization involves defining what actions and resources users or nodes are allowed to access or modify.</li><li>Data Encryption: Encrypting data in transit and at rest is crucial for maintaining data confidentiality and integrity.</li><li>Secure Communication: Ensuring secure communication between distributed nodes is essential. Secure Socket Layer (SSL) and Transport Layer Security (TLS) are commonly used protocols to encrypt data during transmission.</li><li>Firewalls: Firewalls are used to filter network traffic and prevent unauthorized access to a network or system. They can be implemented at the perimeter of the network or on individual nodes.</li><li>ntrusion Detection and Prevention Systems (IDPS): IDPS are designed to identify and respond to potential security threats or breaches in real-time.</li><li>Vulnerability Assessment: Regularly scanning and assessing the security of distributed systems is vital. Vulnerability assessment tools help identify weaknesses and potential entry points for attackers.</li><li>Security Policies and Procedures: Establishing security policies and procedures is essential for ensuring that security practices are consistently followed.</li><li>Patch Management: Keeping software and systems up to date with the latest security patches is crucial. Vulnerabilities in software are often exploited by attackers, so timely patch management is essential.</li><li>Distributed Denial of Service (DDoS) Protection: DDoS attacks can overwhelm a distributed system by flooding it with traffic.</li><li>Cryptography: Cryptography plays a significant role in securing data and communication in distributed systems.</li><li>Security Audits and Logging: Implementing security audits and logging mechanisms can help track and analyze system activity. This is useful for detecting and investigating security incidents.</li><li>Incident Response: Developing an incident response plan is crucial to minimize the impact of security breaches.</li><li>Compliance: Compliance standards like HIPAA, GDPR, and PCI DSS have specific security requirements that distributed systems must adhere to.</li><li>User Education: Educating users and administrators about security best practices, such as strong password management and safe browsing habits, is an important aspect of security.</li></ol><h4><strong>Data distribution:</strong></h4><p>Data distribution is a key concept in distributed systems and databases. It involves the storage and management of data across multiple nodes, often in geographically dispersed locations. Data distribution is essential for achieving scalability, high availability, fault tolerance, and efficient data access in distributed systems. Here are some important aspects of data distribution:</p><ol><li>Data Partitioning: Data partitioning, also known as sharding, is the process of dividing a dataset into smaller subsets called partitions or shards. Each shard is stored on a separate node or database server.</li><li>Replication: Replication involves maintaining multiple copies of data on different nodes. Data replication is used to enhance fault tolerance, improve read performance, and ensure data availability.</li><li>Consistency Models: When distributing data across multiple nodes or replicas, it’s essential to define the consistency model to determine how and when data updates are propagated.</li><li>Data Synchronization: Ensuring that data remains consistent across distributed nodes is crucial. Techniques like two-phase commit (2PC), quorum-based systems, and conflict resolution mechanisms help maintain data synchronization.</li><li>Data Distribution Strategies.</li><li>Data Caching: Caching frequently accessed data on distributed nodes or in-memory caches helps reduce the load on primary data sources and improves response times.</li><li>Data Distribution Algorithms: Various algorithms are used to determine how data is distributed across nodes, including consistent hashing and range-based partitioning.</li><li>Load Balancing: Load balancing mechanisms are used to distribute client requests evenly across nodes to prevent overloading a single node. This ensures optimal resource utilization and high availability.</li><li>Data Movement and Migration: When scaling or reorganizing the distributed system, data movement and migration strategies must be in place to move data from one node to another without compromising system performance.</li><li>Global Data Distribution: In scenarios where data needs to be distributed globally, techniques like content delivery networks (CDNs) or edge computing can be used to reduce latency and improve data access for users in different regions.</li><li>Distributed Databases: Distributed database systems are specifically designed to handle data distribution across multiple nodes. Examples include Apache Cassandra, Amazon DynamoDB, and Google Spanner.</li><li>Data Versioning: Keeping track of different versions of data in a distributed system can be important for auditing, conflict resolution, and ensuring data consistency.</li></ol><h4><strong>Scalable architectural patterns:</strong></h4><p>Scalable architectural patterns are design approaches used in software and system architecture to ensure that a system can efficiently grow and handle increased workloads as demand increases. Scalability is a crucial consideration in modern computing, especially in the context of web services, cloud computing, and large-scale applications. Here are some commonly used scalable architectural patterns:</p><ol><li>Microservices Architecture: Microservices is an architectural pattern in which an application is broken down into small, loosely coupled services that can be developed, deployed, and scaled independently.</li><li>Service-Oriented Architecture (SOA): SOA is an architectural pattern where an application is composed of loosely coupled services that communicate with each other through standard protocols.</li><li>Event-Driven Architecture: In an event-driven architecture, components of a system communicate by generating and reacting to events.</li><li>Serverless Computing: Serverless architecture abstracts away infrastructure management, and developers only focus on writing code in the form of functions or microservices.</li><li>Elastic Scalability: Elastic scalability is a pattern where resources, such as virtual machines or containers, are automatically scaled up or down based on real-time demand.</li><li>Load Balancing: Load balancing distributes incoming network traffic across multiple server instances to ensure that no single server is overwhelmed.</li><li>Caching: Caching involves storing frequently accessed data in a cache, which allows for faster retrieval and reduces the load on backend systems.</li><li>Distributed Databases: Distributed database systems distribute data across multiple nodes or clusters to handle large datasets and provide high availability.</li><li>Content Delivery Networks (CDNs): This pattern reduces latency and improves the scalability and availability of content delivery for websites and applications.</li><li>Message Queues: Message queuing systems, such as Apache Kafka or RabbitMQ, enable asynchronous communication between distributed components.</li><li>Stateless Architectures: Stateless architectures store session state outside the application servers, which allows for easier horizontal scaling.</li><li>Horizontal Scaling: Horizontal scaling involves adding more instances of a component, such as web servers, to handle increased load.</li><li>Auto-Scaling: Auto-scaling is a pattern that automatically adds or removes resources in response to varying workloads. Cloud providers offer auto-scaling features to ensure that systems are appropriately sized.</li><li>Sharding: Sharding is a technique for distributing data across multiple databases or data stores. It’s commonly used to improve data access performance and scalability in large systems.</li><li>Polyglot Persistence: Polyglot persistence involves using multiple data storage technologies within a system to best fit the needs of different components.</li></ol><h4><strong>Message queues:</strong></h4><p>Message queues are a fundamental component of distributed systems and play a vital role in enabling asynchronous communication and decoupling of components or services. They are used to improve the performance, reliability, and scalability of systems by allowing different parts of the system to communicate without being dependent on each other.</p><p>Key Components of Message Queues:</p><ul><li>Message: A message is a piece of data or a request that is placed in the queue for processing.</li><li>Message Queue: The queue itself is a buffer that stores messages until they are consumed by one or more consumers.</li><li>Producer: A producer is responsible for creating and sending messages to the message queue.</li><li>Consumer: A consumer is responsible for retrieving and processing messages from the queue.</li><li>Middleware: Middleware software or a message broker manages the message queue. It provides features like message routing, delivery guarantees, and scalability.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90eb45da123a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Design Pattern.]]></title>
            <link>https://medium.com/@gethikashalani/software-design-pattern-be97457ff4d9?source=rss-28d9a1d6ceeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/be97457ff4d9</guid>
            <category><![CDATA[software-design-patterns]]></category>
            <dc:creator><![CDATA[Geethika Shalani]]></dc:creator>
            <pubDate>Mon, 28 Aug 2023 15:37:27 GMT</pubDate>
            <atom:updated>2023-08-29T15:57:32.380Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*iGnDP3sJBudLXohCNuhXlA.png" /></figure><h3><strong>What is software design patterns?</strong></h3><p>Software design patterns are general reusable solutions to common problems that developers face when designing and implementing software applications. They represent best practices and proven solutions that have evolved over time to help address various design challenges. Design patterns provide a common vocabulary for developers to communicate about these solutions and promote better code organization, maintainability, and extensibility.</p><h3>The origin of the design pattern.</h3><p>The concept of design patterns in software development originated from the field of architecture, where architects have long used recurring solutions to common problems in building design. In the context of software, the concept was popularized by a book called “Design Patterns: Elements of Reusable Object-Oriented Software,” written by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, often referred to as the “Gang of Four” (GoF). The book was published in 1994 and is considered one of the foundational texts in the field of software engineering.</p><p>The Gang of Four introduced the idea of design patterns as reusable solutions to common problems in software design. They identified 23 design patterns, categorized into creational, structural, and behavioral patterns, along with examples and guidelines on how to implement them.</p><p>The book’s impact was significant and transformative in the software development community. It provided a shared vocabulary and a systematic approach to solving recurring design problems. By adopting these patterns, software developers could leverage proven solutions and design principles, leading to more maintainable, modular, and scalable code.</p><p>The Gang of Four book presented design patterns as building blocks for constructing object-oriented software systems. Over time, the concept of design patterns has expanded to cover various programming paradigms, languages, and architectural styles. As the software development field has evolved, many new design patterns have been identified and documented to address a broader range of challenges.</p><p>The success of the design patterns concept led to the emergence of pattern languages, conferences, and online resources dedicated to discussing and sharing new patterns and best practices. Today, design patterns continue to be an essential part of software engineering education and practice, helping developers create high-quality software systems by drawing on the collective wisdom of experienced practitioners.</p><h3><strong>What is the use of software design patterns?</strong></h3><p>Software design patterns serve several important purposes in the field of software development:</p><ol><li><strong>Reusable Solutions: </strong>Design patterns provide proven, reusable solutions to common design problems. Instead of reinventing the wheel for each new project, developers can leverage these established patterns to solve similar problems efficiently.</li><li><strong>Best Practices:</strong> Patterns encapsulate best practices and design principles that have been refined over time. By using these patterns, developers can implement code that follows industry-standard guidelines, improving the overall quality and maintainability of the software.</li><li><strong>Abstraction and Communication:</strong> Design patterns provide a common vocabulary and abstraction that developers can use to communicate about complex design concepts. This common understanding helps teams collaborate more effectively, reducing misunderstandings and facilitating discussions about the software’s architecture.</li><li><strong>Scalability and Maintainability:</strong> Patterns encourage modular and well-structured code. This modular approach makes it easier to extend, modify, and maintain the software over its lifecycle, as changes can be localized to specific components without affecting the entire system.</li><li><strong>Separation of Concerns:</strong> Many design patterns promote the separation of different concerns in the software, such as separating UI from business logic or data access. This separation improves code organization and makes it easier to manage and update individual components.</li><li><strong>Flexibility and Adaptability: </strong>Design patterns often provide flexible ways to incorporate new features or alter existing behavior without major code changes. This adaptability is crucial as software requirements evolve over time.</li><li><strong>Code Reusability: </strong>Patterns encourage code reuse by providing generalized solutions. Developers can use and adapt these patterns in various parts of their applications, which leads to more efficient development and fewer errors.</li><li><strong>Documentation:</strong> Patterns inherently document solutions to common problems. Developers can look at a design pattern and understand the rationale behind certain design decisions, helping them grasp the intent of the code more easily.</li><li><strong>Consistency:</strong> When a team or organization follows a set of design patterns, it fosters a consistent approach to solving problems. This consistency makes it easier for developers to understand and work on each other’s code.</li><li><strong>Learning and Skill Development:</strong> Learning about design patterns enhances developers’ understanding of software architecture and design principles. Applying these patterns helps developers improve their problem-solving skills and become better software architects.</li><li><strong>Maintaining Legacy Code:</strong> When inheriting or working on legacy code, design patterns can offer insights into the existing structure and design choices, making it easier to navigate and update the codebase.</li></ol><h3><strong>How many software patterns are there?</strong></h3><p>23 design patterns.</p><p>These patterns are organized into three categories: <em>creational patterns, structural patterns, </em>and <em>behavioral patterns</em>. Each pattern addresses a specific type of design problem and provides a reusable solution. Here is a brief overview of each pattern:</p><p>Creational Patterns:</p><ol><li><strong>Singleton:</strong> Ensures a class has only one instance and provides a global point of access to that instance.</li><li><strong>Factory Method: </strong>Defines an interface for creating objects but allows subclasses to decide which class to instantiate.</li><li><strong>Abstract Factory:</strong> Provides an interface for creating families of related or dependent objects.</li><li><strong>Builder: </strong>Separates the construction of a complex object from its representation, allowing the same construction process to create different representations.</li><li><strong>Prototype:</strong> Creates new objects by copying an existing object’s attributes, allowing for the creation of new instances without explicitly specifying their classes.</li></ol><p>6.<strong> Adapter: </strong>Converts the interface of a class into another interface that clients expect, allowing classes with incompatible interfaces to work together.</p><p>Structural Patterns:</p><ol><li><strong>Bridge:</strong> Separates an abstraction from its implementation, enabling both to change independently.</li><li><strong>Composite:</strong> Composes objects into tree structures to represent part-whole hierarchies. Clients treat individual objects and compositions of objects uniformly.</li><li><strong>Decorator:</strong> Dynamically adds responsibilities to objects without modifying their code.</li><li><strong>Facade:</strong> Provides a unified interface to a set of interfaces in a subsystem, simplifying the usage of complex systems.</li><li><strong>Flyweight:</strong> Shares instances of objects to support a large number of fine-grained objects efficiently.</li><li><strong>Chain of Responsibility: </strong>Passes a request along a chain of handlers, allowing multiple objects to handle the request.</li></ol><p>Behavioral Patterns:</p><ol><li><strong>Command: </strong>Turns a request into a stand-alone object, decoupling the sender and receiver.</li><li><strong>Interpreter:</strong> Provides a way to evaluate language grammar or expressions.</li><li><strong>Iterator: </strong>Provides a way to access elements of a collection sequentially without exposing its underlying representation.</li><li><strong>Mediator:</strong> Defines an object that encapsulates how a set of objects interact, promoting loose coupling.</li><li><strong>Memento: </strong>Allows an object’s state to be captured and restored, providing undo and redo functionality.</li><li><strong>Observer: </strong>Defines a dependency between objects, ensuring that when one object changes state, its dependents are notified and updated automatically.</li><li><strong>State:</strong> Allows an object to change its behavior when its internal state changes.</li><li><strong>Strategy:</strong> Defines a family of algorithms, encapsulates each one, and makes them interchangeable. Clients can choose the desired algorithm without modifying the client’s code.</li><li><strong>Template Method:</strong> Defines the structure of an algorithm but lets subclasses override specific steps.</li><li><strong>Visitor:</strong> Separates an algorithm from an object’s structure, allowing new operations to be added to objects without modifying their code.</li><li><strong>Proxy:</strong> Provides a placeholder for another object to control its access, acting as an intermediary to control access, add functionality, or defer object creation.</li></ol><h3><strong>Which design pattern is used most?</strong></h3><p>The popularity and usage of design patterns can vary based on factors such as the programming language, technology stack, industry, and the specific problem being addressed. However, among the 23 original design patterns introduced by the Gang of Four, a few patterns are often considered more commonly used due to their broad applicability:</p><ol><li><strong>Singleton:</strong> The Singleton pattern is widely used when you want to ensure that a class has only one instance and provide a global point of access to that instance. It’s commonly used for managing resources that should be shared across the application, such as configuration settings, database connections, and logging.</li></ol><p>Key characteristics of the Singleton pattern:</p><p><strong>Private Constructor:</strong> The Singleton class typically has a private constructor, preventing other classes from directly instantiating it.</p><p><strong>Private Instance:</strong> The Singleton class holds a private static instance of itself, which is the sole instance of the class.</p><p><strong>Static Access Method:</strong> The Singleton class provides a static method that allows other classes to access the single instance. This method is often named getInstance().</p><p><strong>Lazy Initialization (Optional): </strong>The instance is created only when the getInstance() method is called for the first time. This is called lazy initialization and is not always necessary, depending on the requirements.</p><p><strong>2 . Factory Method:</strong> The Factory Method pattern is frequently used for creating objects in a way that allows subclasses to determine the type of objects that will be created. It’s particularly useful when you have a family of related classes and want to delegate the responsibility of object creation to subclasses.</p><p>Key components of the Factory Method pattern:</p><p><strong>Creator (Abstract Class or Interface): </strong>Declares the factory method, which is responsible for creating objects. It may also include other methods that use the products created by the factory method.</p><p><strong>Concrete Creator Subclasses:</strong> Implement the factory method, determining which concrete class to instantiate. These subclasses are responsible for creating specific instances of products.</p><p><strong>Product (Abstract Class or Interface):</strong> Defines the common interface for the objects that the factory method creates.</p><p><strong>Concrete Product Classes:</strong> Implement the product interface defined by the abstract product. These are the actual objects that the factory method produces.</p><p><strong>3. Observer:</strong> The Observer pattern is used to establish a one-to-many dependency between objects, where changes in one object (the subject) are automatically communicated to and reflected in other objects (observers). This pattern is used for implementing event handling, pub-sub systems, and UI components that need to respond to changes in data.</p><p><strong>4. Decorator:</strong> The Decorator pattern is commonly used for adding responsibilities to objects dynamically, without altering their structure. It’s useful for situations where you want to extend the functionality of objects without modifying their existing code.</p><p><strong>5. Strategy:</strong> The Strategy design pattern is a behavioral pattern that defines a family of algorithms, encapsulates them in separate classes, and makes them interchangeable. This pattern allows a client to choose an algorithm from a family of algorithms dynamically, without altering the client’s code. Here are the key characteristics of the Strategy pattern:</p><p><strong>Encapsulation of Algorithms:</strong> The Strategy pattern encapsulates different algorithms or strategies in separate classes. Each class represents a specific algorithm or behavior.</p><p><strong>Interface or Base Class:</strong> Strategies are often defined using an interface or a base class. This common interface ensures that all strategies have a consistent method signature, allowing them to be used interchangeably.</p><p><strong>Variability: </strong>The Strategy pattern is used to manage variability in an application. It allows you to define multiple strategies and switch between them at runtime or during configuration, without affecting the client code.</p><p><strong>Composition over Inheritance</strong>: The Strategy pattern promotes composition over inheritance. Instead of relying on inheritance to define behavior, strategies are composed by creating instances of the strategy classes and injecting them into the context.</p><p><strong>Client-Strategy Interaction:</strong> The client interacts with a context object that holds a reference to the chosen strategy. The client can request the context to perform a specific action, which is then delegated to the selected strategy.</p><p><strong>Run-Time Flexibility:</strong> Since strategies are interchangeable, you can change the behavior of an application at runtime by changing the strategy assigned to the context. This eliminates the need to modify client code when behavior changes.</p><p><strong>Code Reusability:</strong> The Strategy pattern promotes code reusability by encapsulating behavior in separate classes. This makes it easy to reuse strategies across different parts of the application.</p><p><strong>Open/Closed Principle:</strong> The Strategy pattern aligns with the Open/Closed Principle, which states that software entities (classes, modules, functions, etc.) should be open for extension but closed for modification. New strategies can be added without changing existing code.</p><p><strong>6. Adapter:</strong> The Adapter pattern is frequently used to convert the interface of a class into another interface that clients expect. It’s useful for integrating components with incompatible interfaces, such as using legacy code in a modern system.</p><p><strong>7. MVC (Model-View-Controller):</strong> While not one of the original Gang of Four patterns, the MVC pattern is one of the most widely used architectural patterns. It separates an application into three interconnected components: Model (data and business logic), View (presentation and UI), and Controller (handles user input and manages interaction).</p><h3><strong>What is the Factory Method Pattern?</strong></h3><p>The Factory Method pattern is a creational design pattern that provides an interface for creating objects but allows subclasses to decide which class to instantiate. It defines an abstract class or interface (the “creator”) with a method (the “factory method”) that creates objects. Subclasses of the creator implement this factory method to produce instances of specific classes that inherit from a common parent class.</p><p>The Factory Method pattern promotes loose coupling between client code and the classes being instantiated. It allows you to encapsulate the object creation process and delegate the responsibility of creating objects to subclasses. This way, the client code does not need to know the specific class being instantiated; it only interacts with the factory method through the common interface.</p><p>Key components of the Factory Method pattern:</p><ol><li><strong>Creator (Abstract Class or Interface):</strong> Declares the factory method, which is responsible for creating objects. It may also include other methods that use the products created by the factory method.</li><li>Concrete Creator Subclasses: Implement the factory method, determining which concrete class to instantiate. These subclasses are responsible for creating specific instances of products.</li><li>Product (Abstract Class or Interface): Defines the common interface for the objects that the factory method creates.</li><li>Concrete Product Classes: Implement the product interface defined by the abstract product. These are the actual objects that the factory method produces.</li></ol><h3><strong>What is the importance of pattern development?</strong></h3><p>Pattern development, in the context of software design, refers to the process of identifying, documenting, and sharing new design patterns. The importance of pattern development lies in its ability to enhance software engineering practices, facilitate communication, and improve the overall quality of software systems. Here are some key reasons why pattern development is important:</p><ol><li><strong>Problem Solving:</strong> New and emerging challenges in software development often require innovative solutions. Developing new patterns helps address specific problems that existing patterns might not cover adequately.</li><li><strong>Best Practices:</strong> Patterns encapsulate best practices and proven solutions to common design problems. Developing new patterns allows the software development community to share novel ways of solving problems effectively and efficiently.</li><li><strong>Adaptation to New Technologies:</strong> As technologies evolve, new patterns may be required to address the unique design challenges posed by these technologies. Developing patterns for new platforms, frameworks, or paradigms helps guide developers in making optimal design decisions.</li><li><strong>Domain-Specific Solutions:</strong> Certain domains or industries have specific requirements that may not be fully covered by existing patterns. Developing domain-specific patterns helps tailor solutions to the unique needs of those domains.</li><li><strong>Educational Purposes: </strong>Developing new patterns is an educational process that encourages deeper understanding of software design principles. It helps developers refine their design skills and encourages critical thinking.</li><li><strong>Efficient Communication: </strong>Patterns provide a common vocabulary for developers to communicate about design decisions and architectural choices. Developing new patterns allows teams to communicate effectively and share insights about effective design strategies.</li><li><strong>Continuous Improvement: </strong>The field of software development is constantly evolving. Developing new patterns fosters a culture of continuous improvement, encouraging developers to refine and optimize their design approaches.</li><li><strong>Encouraging Creativity:</strong> The process of pattern development encourages creativity and exploration of new ideas. It enables developers to experiment with different solutions and discover innovative ways of solving problems.</li><li><strong>Documentation of Solutions: </strong>Developing patterns documents solutions to specific problems in a standardized and reusable format. This documentation is valuable for developers who encounter similar challenges in the future.</li><li><strong>Sharing Knowledge:</strong> Patterns are a means of sharing knowledge within the software development community. By developing new patterns, experienced developers can pass on their insights and expertise to others.</li><li><strong>Legacy Code Maintenance: </strong>Developing patterns for dealing with legacy code can provide strategies for modernizing and improving existing systems.</li><li><strong>Consistency: </strong>As new patterns are developed and adopted, they contribute to a consistent and standardized approach to software design. This consistency improves the quality and maintainability of software systems.</li></ol><h3><strong>How do design patterns solve problems?</strong></h3><ol><li><strong>Identifying Common Problems: </strong>Design patterns are developed based on the recognition that certain design problems recur across different software projects. These problems could involve object creation, interaction between objects, code organization, and more.</li><li><strong>Providing Generalized Solutions:</strong> Each design pattern encapsulates a generalized solution that has proven effective in solving a particular problem. These solutions are based on best practices, architectural principles, and the collective experience of the software development community.</li><li><strong>Promoting Reusability:</strong> Patterns are reusable templates that developers can apply to different situations. Instead of reinventing the wheel for every new problem, developers can leverage existing patterns to solve similar problems efficiently.</li><li><strong>Improving Maintainability: </strong>Design patterns promote code organization and modularity. By following the structure and guidelines of a pattern, developers create code that is easier to maintain, update, and extend over time.</li><li><strong>Enforcing Design Principles:</strong> Patterns often embody fundamental design principles such as separation of concerns, loose coupling, and encapsulation. Applying patterns encourages developers to adhere to these principles, leading to cleaner and more robust designs.</li><li><strong>Facilitating Communication: </strong>Patterns provide a common vocabulary for developers to discuss design decisions. When a pattern is applied, team members can understand the intended design and its benefits without extensive explanation.</li><li><strong>Consistency: </strong>Design patterns foster consistency in design approaches. When multiple developers apply the same patterns, it leads to a consistent and recognizable structure across the codebase.</li><li><strong>Solving Complex Interactions:</strong> Patterns help address complex interactions between objects or components in a structured manner. They define clear roles and responsibilities for each part of the system, reducing ambiguity.</li><li><strong>Flexibility and Adaptability:</strong> Many patterns enable systems to be more flexible and adaptable to changes. By separating concerns and using patterns like Strategy or Observer, you can alter behavior or respond to changes without modifying existing code extensively.</li><li><strong>Preventing Antipatterns:</strong> Antipatterns are design choices that seem reasonable but lead to suboptimal outcomes. Design patterns provide a positive alternative to these antipatterns, guiding developers away from problematic solutions.</li><li><strong>Documenting Solutions:</strong> Patterns document the rationale behind specific design decisions. This documentation helps future developers understand the reasoning behind a design, making it easier to maintain and extend the software.</li><li><strong>Enhancing Code Quality: </strong>By following established patterns, developers produce higher-quality code that is well-structured, modular, and adheres to proven architectural principles.</li></ol><h3>Purpose of software design pattern.</h3><p>Software design patterns serve several important purposes in the field of software engineering:</p><ol><li><strong>Reusable Solutions: </strong>Patterns encapsulate proven solutions to recurring design problems. Instead of reinventing the wheel, developers can leverage these patterns to solve common issues in a consistent and efficient manner.</li><li><strong>Common Vocabulary:</strong> Patterns provide a shared vocabulary and understanding among developers. When discussing design decisions, using well-known patterns helps team members communicate more effectively.</li><li><strong>Best Practices:</strong> Patterns embody best practices and design principles. They guide developers in structuring code and systems in ways that promote maintainability, extensibility, and readability.</li><li><strong>Abstraction: </strong>Patterns promote abstraction and modularity by breaking down complex systems into smaller, manageable components. This allows developers to focus on individual parts without getting overwhelmed by the entire system.</li><li><strong>Flexibility: </strong>Patterns make code more adaptable to changes. By following established patterns, developers can make modifications to specific parts of the codebase without affecting the entire system.</li><li><strong>Design Evolution:</strong> Patterns provide a basis for evolving software designs. As requirements change or new features are added, patterns can guide how to integrate these changes while maintaining the overall architecture.</li><li><strong>Problem Solving:</strong> Patterns offer solutions to design challenges that developers commonly encounter, saving time and effort in finding appropriate solutions for specific contexts.</li><li><strong>Code Understandability: </strong>Patterns enhance code readability and comprehension. Developers familiar with patterns can quickly understand the intent and structure of a piece of code, even if they’re new to a project.</li><li><strong>Code Maintainability:</strong> Patterns contribute to code that is easier to maintain over time. By following established patterns, developers create consistent and organized codebases that are less prone to becoming unmaintainable “spaghetti code.”</li><li><strong>Architectural Guidance:</strong> Some patterns guide the high-level architecture of software systems, providing a roadmap for structuring components, interactions, and responsibilities.</li><li><strong>Learning Aid:</strong> Patterns help junior developers learn from experienced developers’ knowledge and experiences. Studying and applying patterns can accelerate the learning curve for newcomers to software engineering.</li><li><strong>Design Communication:</strong> Patterns enable designers to communicate design decisions effectively to other team members, stakeholders, and across different development teams.</li></ol><h3><strong>Software Design Patterns VS Design Principles.</strong></h3><p>Software design patterns and design principles are two distinct concepts that play crucial roles in the field of software engineering. While they are related and often complement each other, they serve different purposes and focus on different aspects of software design.</p><h4><strong>Software Design Patterns:</strong></h4><p>Design patterns are reusable solutions to common design problems. They are specific templates that outline how to structure code to solve particular issues that software developers frequently encounter. Design patterns provide a higher-level approach to solving problems, offering guidelines for organizing classes, objects, and interactions within a system. Examples of design patterns include the Singleton pattern, Observer pattern, and Factory pattern. Design patterns help developers create more maintainable, scalable, and flexible code by following proven best practices.</p><h4><strong>Design Principles:</strong></h4><p>Design principles, on the other hand, are general guidelines and concepts that inform the overall approach to software design. They focus on foundational concepts that guide developers in making design decisions and shaping the architecture of a software system. These principles offer high-level guidance and help developers create software that is modular, loosely coupled, and easy to understand. Some well-known design principles include SOLID (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) and the DRY (Don’t Repeat Yourself) principle. Design principles provide a framework for making decisions about class organization, inheritance, encapsulation, and more.</p><h4><strong>Relationship Between Design Patterns and Design Principles:</strong></h4><p>Design patterns often embody design principles. For instance, the SOLID principles are essential to understanding and implementing many design patterns. Design principles provide the fundamental concepts that guide the creation of design patterns. Patterns, in turn, provide concrete implementations of those principles in specific scenarios</p><h3>Popular Software Architectural Patterns.</h3><p>Although somewhat outside the scope of this guide, it is important to mention that there are also architectural patterns that can be applied to the design of the software as a whole. What is an architectural pattern? A general, reusable solution to common problems in architecture (see how the definition is almost the same for software design?). These three design patterns are similar, with different sets of dependencies and levels of binding.</p><h4>1. MVC Design Pattern</h4><p>The Model-View-Controller (MVC) design pattern is a software architectural pattern commonly used in the development of user interfaces for applications. It aims to separate the concerns of an application’s logic, user interface, and data presentation in order to enhance maintainability, reusability, and scalability.</p><p>MVC is composed of three main components:</p><ol><li>Model: The Model represents the core business logic and data of the application. It is responsible for managing the data, processing user inputs, and maintaining the application’s state. The Model does not have direct knowledge of the user interface or how the data is presented.</li><li>View: The View is responsible for presenting the data to the user. It displays the information provided by the Model and handles user interface elements like buttons, labels, and forms. The View is passive and does not contain business logic. It receives updates from the Model and reflects any changes in the data.</li><li>Controller: The Controller acts as an intermediary between the Model and the View. It handles user input and translates it into actions that the Model should take. The Controller updates the Model based on user input and may also update the View to reflect changes in the Model’s data. In essence, the Controller manages the flow of data and interactions between the Model and the View.</li></ol><p>The key benefits of using the MVC design pattern include:</p><ul><li>Separation of Concerns: MVC enforces a clear separation between the application’s logic, user interface, and data presentation. This makes the codebase more organized and easier to maintain.</li><li>Modularity and Reusability: Because each component has a distinct responsibility, it’s easier to reuse and replace components as needed without affecting the entire system.</li><li>Parallel Development: Different teams can work on different components simultaneously. For example, designers can work on the View while developers focus on the Model and Controller.</li><li>Testability: Each component can be tested independently, making it easier to write unit tests and ensure the quality of the code.</li><li>Scalability: As the application grows, MVC’s separation of concerns makes it easier to manage and extend the codebase without major overhauls.</li></ul><p>It’s important to note that there are variations and adaptations of the MVC pattern, such as Model-View-Presenter (MVP) and Model-View-ViewModel (MVVM), each with their own nuances and use cases. These variations often arise to address specific needs of different platforms and technologies.</p><h4>2. MVP Design Pattern</h4><p>The Model-View-Presenter (MVP) design pattern is another software architectural pattern commonly used in the development of user interfaces for applications, particularly in the context of GUI-based applications. Like the MVC pattern, MVP aims to separate the concerns of an application’s logic, user interface, and data presentation to enhance maintainability and testability.</p><p>MVP consists of three main components:</p><ol><li>Model: Similar to the Model in the MVC pattern, the Model in MVP represents the core business logic, data, and state of the application. It handles data processing, storage, and manipulation. The Model is independent of the user interface and does not have direct knowledge of it.</li><li>View: The View in MVP is responsible for displaying data to the user and capturing user inputs. Unlike the View in MVC, the MVP View is typically more passive and dumb. It delegates user interactions to the Presenter and listens for updates from the Presenter to update its display.</li><li>Presenter: The Presenter acts as an intermediary between the Model and the View. It receives user input from the View and processes it by interacting with the Model. The Presenter contains the application logic, including data retrieval, transformation, and manipulation. After processing, the Presenter updates the View to reflect the changes in the data.</li><li>In MVP, the key distinction from MVC lies in the role of the Presenter. While in MVC, the Controller manages the flow of data and interactions between the Model and the View, in MVP, the Presenter takes on a more active role by handling user interactions and application logic.</li></ol><p>The benefits of using the MVP design pattern include:</p><ul><li>Separation of Concerns: Similar to MVC, MVP enforces a clear separation between the different concerns of the application, leading to a more modular and maintainable codebase.</li><li>Testability: The passive nature of the View and the centralization of application logic in the Presenter make it easier to write unit tests for both the View and the Presenter. The Model can also be tested independently.</li><li>Code Reusability: Because the application logic is concentrated in the Presenter, it can be reused across different Views. This is particularly useful when you have multiple user interfaces (e.g., desktop and mobile) that need to interact with the same logic.</li><li>Ease of Collaboration: MVP can make it easier for designers and developers to work concurrently, as the View and Presenter are more decoupled compared to MVC.</li></ul><p>MVP, like any design pattern, is not a one-size-fits-all solution. It’s important to consider the specific requirements of your application and the technologies you’re using when deciding whether to adopt MVP or another pattern.</p><h4>3. MVVM Design Pattern</h4><p>The Model-View-ViewModel (MVVM) design pattern is a software architectural pattern primarily used for developing user interfaces, especially in the context of applications with graphical user interfaces (GUIs) and data-binding capabilities. MVVM is designed to promote separation of concerns, maintainability, and ease of testing in applications.</p><p>MVVM consists of three main components:</p><ol><li>Model: Similar to other patterns like MVC and MVP, the Model represents the application’s business logic, data, and state. It handles data processing, storage, and manipulation independently of the user interface components.</li><li>View: The View in MVVM represents the user interface elements and their layout. However, unlike in MVC and MVP, the View in MVVM is more closely tied to the ViewModel through data-binding mechanisms. The View is responsible for displaying data and handling user interactions, but it doesn’t contain the application logic.</li><li>ViewModel: The ViewModel is a crucial part of MVVM. It acts as an intermediary between the Model and the View. The ViewModel provides data and behaviors that the View can directly bind to. It prepares and structures the data from the Model in a way that is easy to display and interact with in the View. The ViewModel also contains presentation logic, which includes formatting data for display and handling user input. Unlike the Presenter in MVP, the ViewModel is more closely integrated with the View through data-binding mechanisms.</li></ol><p>Key features and benefits of the MVVM design pattern include:</p><ul><li>Data Binding: One of the core strengths of MVVM is its data-binding capability, which allows automatic synchronization of data between the View and the ViewModel. Changes in the ViewModel are automatically reflected in the View, and vice versa.</li><li>Separation of Concerns: MVVM enforces a clear separation between the application’s logic, user interface, and data presentation, making the codebase more modular and easier to maintain.</li><li>Testability: The separation of the ViewModel from the View allows for easier unit testing of the ViewModel’s business logic and presentation logic. Mocking data and testing different scenarios becomes simpler.</li><li>Reusability: Similar to the MVP pattern, the ViewModel can be reused across different Views. This is particularly useful when building applications for different platforms that share the same underlying logic.</li><li>User Interface Flexibility: Since the ViewModel prepares and structures data for display, it provides flexibility in adapting the same data to different user interface layouts and requirements.</li></ul><p>MVVM is commonly used with frameworks that provide robust data-binding mechanisms, such as WPF (Windows Presentation Foundation) for desktop applications and frameworks like Angular and Vue.js for web applications. However, it’s important to note that implementing MVVM can introduce additional complexity, especially when dealing with complex data flows and synchronization between the View and ViewModel.</p><h3><strong>Disadvantages of software design patterns.</strong></h3><p>While software design patterns offer numerous benefits, they are not without their disadvantages and limitations. Here are some potential disadvantages of using software design patterns:</p><ol><li><strong>Overengineering:</strong> One of the main drawbacks of design patterns is the risk of overengineering. Developers might feel compelled to use patterns even when they’re not necessary for the current project. This can lead to unnecessary complexity, making the codebase harder to understand and maintain.</li><li><strong>Learning Curve:</strong> Learning and understanding design patterns can be challenging, especially for junior developers or those new to software engineering. Applying patterns correctly requires a solid understanding of the underlying principles, which can take time to acquire.</li><li><strong>Applicability:</strong> Not all design patterns are suitable for every project. Using a pattern that doesn’t align with the project’s requirements or architecture can lead to unnecessary complications and inefficiencies.</li><li><strong>Code Obfuscation: </strong>If design patterns are applied excessively or inappropriately, the code can become convoluted and hard to follow. The purpose of design patterns is to improve code readability and maintainability, but if used improperly, they can have the opposite effect.</li><li><strong>Overhead:</strong> Some design patterns introduce additional layers of abstraction and indirection, which can lead to performance overhead. While this might not be a concern in many cases, it’s important to consider performance implications when applying certain patterns.</li><li><strong>Maintenance Burden:</strong> Over time, design patterns can become outdated or may not fit the evolving needs of a project. Updating or modifying patterns can introduce challenges and may require significant refactoring.</li><li><strong>Complexity:</strong> Some design patterns introduce complexity in order to achieve flexibility or extensibility. While this is often beneficial, it can also make the codebase harder to understand, especially for developers who are not familiar with the specific pattern being used.</li><li><strong>Standardization Pressure: </strong>Following design patterns too rigidly can lead to a mindset where developers feel compelled to fit every aspect of the code into predefined patterns. This can hinder creativity and innovative problem-solving.</li><li><strong>Project Size:</strong> Some design patterns are more suited for larger, complex projects. Applying these patterns to smaller projects might result in unnecessary overhead and complicate the codebase.</li><li><strong>Overreliance:</strong> Relying too heavily on design patterns can lead to a lack of critical thinking and creativity in the development process. It’s important to consider the unique aspects of each project and not apply patterns blindly.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be97457ff4d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amazon AWS.]]></title>
            <link>https://medium.com/@gethikashalani/amazon-aws-e1d72216f3b?source=rss-28d9a1d6ceeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1d72216f3b</guid>
            <dc:creator><![CDATA[Geethika Shalani]]></dc:creator>
            <pubDate>Sun, 18 Sep 2022 07:05:03 GMT</pubDate>
            <atom:updated>2022-09-18T09:36:50.937Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*nTJsmphd0auLeAkJ7pBFLQ.jpeg" /></figure><h3><strong>What is AWS?</strong></h3><p><strong>Amazon Web Services(AWS)</strong> is a cloud service from Amazon, which provides services in the form of building blocks, these building blocks can be used to create and deploy any type of application in the cloud.</p><p>These services or building blocks are designed to work with each other, and result in applications that are sophisticated and highly scalable.</p><h3>History of AWS…</h3><ul><li>In the year 2002 — AWS services were launched</li><li>In the year 2006- AWS cloud products were launched</li><li>In the year 2012 — AWS had its first customer event</li><li>In the year 2015- AWS achieved $4.6 billion</li><li>In the year 2016- Surpassed the $10 billion revenue target</li><li>In the year 2016- AWS snowball and AWS snowmobile were launched</li><li>In the year 2019- Released approximately 100 cloud services</li></ul><p>Moving forward, we will learn more about AWS services.</p><h3>How Does AWS Work?</h3><p>AWS usually works in several different configurations depending on the user’s requirements. However, the user must be able to see the type of configuration used and the particular server map with respect to the AWS service.</p><h3>Advantages of AWS…</h3><ol><li>AWS provides a user-friendly programming model, architecture, database as well as operating system that has been already known to employers.</li><li>AWS is a very cost-effective service. There is no such thing as long-term commitments for anything you would like to purchase.</li><li>It offers billing and management for the centralized sector, hybrid computing, and fast installation or removal of your application in any location with few clicks.</li><li>There is no need to pay extra money on running data servers by AWS.</li><li>AWS offers a total ownership cost at very reasonable rates in comparison to other private cloud servers.</li></ol><h3>Disadvantages of AWS…</h3><ol><li>AWS has supportive paid packages for intensive or immediate response. Thus, users might need to pay extra money for that.</li><li>There might be some cloud computing problems in AWS especially when you move to a cloud Server such as backup protection, downtime, and some limited control.</li><li>From region to region, AWS sets some default limitations on resources such as volumes, images, or snapshots.</li><li>If there is a sudden change in your hardware system, the application on the cloud might not offer great performance.</li></ol><h3>AWS Pricing Model…</h3><p>AWS pricing model is very cost-effective which makes it most reliable. For instance, if a user wants to use a cloud server for an hour, AWS asks the user to pay only for an hour. There is no such long-term commitment as five years or 10 years and pay accordingly. Besides, there is an AWS free tier service to increase the potential customers’ affordability by offering free services with AWS servers up to 58 products that help users gain some experience with the AWS platform.</p><h3>AWS Services…</h3><p>Amazon has many services for cloud applications. Let us list down a few key services of the AWS ecosystem and a brief description of how developers use them in their business.</p><p>Amazon has a list of services:</p><ul><li>Compute service</li><li>Storage</li><li>Database</li><li>Networking and delivery of content</li><li>Security tools</li><li>Developer tools</li><li>Management tools</li></ul><h3>Applications of AWS…</h3><p>The most common applications of AWS are storage and backup, websites, gaming, mobile, web, and social media applications. Some of the most crucial applications in detail are as follows:</p><h4>1. Storage and Backup</h4><p>One of the reasons why many businesses use AWS is because it offers multiple types of storage to choose from and is easily accessible as well. It can be used for storage and file indexing as well as to run critical business applications.</p><h4>2. Websites</h4><p>Businesses can host their websites on the AWS cloud, similar to other web applications.</p><h4>3. Gaming</h4><p>There is a lot of computing power needed to run gaming applications. AWS makes it easier to provide the best online gaming experience to gamers across the world.</p><h4>4. Mobile, Web and Social Applications</h4><p>A feature that separates AWS from other cloud services is its capability to launch and scale mobile, e-commerce, and <a href="https://www.simplilearn.com/what-is-saas-article">SaaS applications</a>. API-driven code on AWS can enable companies to build uncompromisingly scalable applications without requiring any OS and other systems.</p><h4>5. Big Data Management and Analytics (Application)</h4><ul><li>Amazon Elastic MapReduced to process large amounts of data via the Hadoop framework.</li><li>Amazon Kinesis to analyze and process the streaming data.</li><li>AWS Glue to handle, extract, transform and load jobs.</li><li>Amazon Elasticsearch Service to enable a team to perform log analysis, and tool monitoring with the help of the open source tool, Elastic-search.</li><li>Amazon Athena to query data.</li><li>Amazon QuickSight to visualize data.</li></ul><h4>6. Artificial Intelligence</h4><ul><li>Amazon Lex to offer voice and text chatbot technology.</li><li>Amazon Polly to translate text-to-speech translation such as Alexa Voice Services and echo devices.</li><li>Amazon Rekognition to analyze the image and face.</li></ul><h4>7. Messages and Notifications</h4><ul><li>Amazon Simple Notification Service (SNS) for effective business or core communication.</li><li>Amazon Simple Email Service (SES) to receive or send emails for IT professionals and marketers.</li><li>Amazon Simple Queue Service (SQS) to enable businesses to subscribe or publish messages to end users.</li></ul><h4>8. Augmented Reality and Virtual Reality</h4><ul><li>Amazon Sumerian service enables users to make the use of AR and VR development tools to offer 3D web applications, E-commerce &amp; sales applications, Marketing, Online education, Manufacturing, Training simulations, and Gaming.</li></ul><h4>9. Game Development</h4><ul><li>AWS game development tools are used by large game development companies that offer developer back-end services, analytics, and various developer tools.</li><li>AWS allows developers to host game data as well as store the data to analyze the gamer’s performance and develop the game accordingly.</li></ul><h4>10. Internet of Things</h4><ul><li>AWS IoT service offers a back-end platform to manage IoT devices as well as data ingestion to database services and AWS storage.</li><li>AWS IoT Button offers limited IoT functionality to hardware.</li><li>AWS Greengrass offers AWS computing for IoT device installation.</li></ul><h3>AWS Pricing Model…</h3><p>AWS pricing model is very cost-effective which makes it most reliable. For instance, if a user wants to use a cloud server for an hour, AWS asks the user to pay only for an hour. There is no such long-term commitment as five years or 10 years and pay accordingly. Besides, there is an AWS free tier service to increase the potential customers’ affordability by offering free services with AWS servers up to 58 products that help users gain some experience with the AWS platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1d72216f3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keys in DBMS.]]></title>
            <link>https://medium.com/@gethikashalani/keys-in-dbms-c43c310b7d0d?source=rss-28d9a1d6ceeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c43c310b7d0d</guid>
            <dc:creator><![CDATA[Geethika Shalani]]></dc:creator>
            <pubDate>Fri, 02 Sep 2022 12:18:38 GMT</pubDate>
            <atom:updated>2022-09-02T13:28:38.878Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*PhgEdeKDeiG5PUyKnmfEtA.jpeg" /></figure><h4><strong>What are Keys in DBMS?</strong></h4><p><strong>KEYS in DBMS</strong> is an attribute or set of attributes which helps you to identify a row(tuple) in a relation(table). They allow you to find the relation between two tables. Keys help you uniquely identify a row in a table by a combination of one or more columns in that table. Key is also helpful for finding unique record or row from the table. Database key is also helpful for finding unique record or row from the table.</p><h4><strong>Why do we require keys in DBMS?</strong></h4><p>We use a key for defining various types of integrity constraints in a database. A table, on the other hand, represents a collection of the records of various events for any relation. Now, there might be thousands of these records, and some of these might even be duplicated.</p><p>Thus, we need a way in which one can identify all of these records uniquely and separately, i.e., without any duplicates. This hassle is removed with the help of keys.</p><p>For example, let us consider a database of all the students who are studying in a college. What attribute of all the students, according to you, will identify each of these people uniquely? We can refer to these students by their names, departments, sections, and year. Similarly, we can also mention only the university roll number and fetch all the other details based on that roll number.</p><p>The keys in DBMS can be a combination of multiple attributes (or columns), or they can be just one single attribute. The primary motive of the keys is to provide every record with a unique identity of its own.</p><h4>What are the different types of Keys in DBMS?</h4><p>Keys are of seven broad types in DBMS:</p><ol><li>Candidate Key</li><li>Primary Key</li><li>Foreign Key</li><li>Super Key</li><li>Alternate Key</li><li>Composite Key</li><li>Unique Key</li><li>Compound Key</li></ol><h4><strong><em>1. Primary Key…</em></strong></h4><p>The primary key refers to a column or a set of columns of a table that helps us identify all the records uniquely present in that table. A table can consist of just one primary key. Also, this primary key cannot consist of the same values reappearing/repeating for any of its rows. All the values of a primary key have to be different, and there should be no repetitions.</p><p>The PK (PRIMARY KEY) constraint that we put on a column/set of columns won’t allow these to have a null value or a duplicate. Any table can consist of only a single primary key constraint. A foreign key (explained below) that refers to it can never change the values present in the primary key.</p><h4><em>2. Super Key…</em></h4><p>A super key refers to the set of all those keys that help us uniquely identify all the rows present in a table. It means that all of these columns present in a table that can identify the columns of that table uniquely act as the super keys.</p><p>A super key is a candidate key’s superset (candidate key has been explained below). We need to pick the primary key of any table from the super key’s set so as to make it the table’s identity attribute.</p><h4>3. Candidate Key…</h4><p>The candidate keys refer to those attributes that identify rows uniquely in a table. In a table, we select the primary key from a candidate key. Thus, a candidate key has similar properties as that of the primary keys that we have explained above. In a table, there can be multiple candidate keys.</p><h4>4. Alternate Key…</h4><p>As we have stated above, any table can consist of multiple choices for the primary key. But, it can only choose one. Thus, all those keys that did not become a primary key are known as alternate keys.</p><h4>5. Foreign Key…</h4><p>Foreign key is used to establish relationships between two tables. A foreign key will require each value in a column or set of columns to match the Primary Key of the referential table. Foreign keys help to maintain data and referential integrity.</p><p>Foreign keys are essential for maintaining a difference between two entities that might be linked with the same information but do not share similar information. In such cases, the tables are linked to maintaining a connection but do not entirely work as a replacement for each other. For instance, any individual working for the marketing department might have marketing department information in its employee table, but that does not mean the table can be similar to the department table held by the marketing department.</p><h4>6. Composite Key…</h4><p>The composite key refers to a set of multiple attributes that help us uniquely identify every tuple present in a table. The attributes present in a set may not be unique whenever we consider them separately. Thus, when we take them all together, it will ensure total uniqueness.</p><h4>7. Unique Key…</h4><p>A unique Key is a column or set of columns that uniquely identify each record in a table. All values will have to be unique in this Key. A unique Key differs from a primary key because it can have only one null value, whereas a primary Key cannot have any null values.</p><p>Among the seven types of keys available in the DBMS, a few other types of keys in SQL are also accessible. The key type is called Artificial Keys. An artificial has no relevance or meaning to the business but is often used to tackle conflicting data management situations. For example, if there is no attribute that comprises all required primary key properties or if the primary keys are complex.</p><h4>8. Compound Key</h4><p><strong>Compound key </strong>has two or more attributes that allow you to uniquely recognize a specific record. It is possible that each column may not be unique by itself within the database. However, when combined with the other column or columns the combination of composite keys become unique. The purpose of the compound key in database is to uniquely identify each record in the table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*KhArnvi18kxkR1WKU4TVNA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c43c310b7d0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evaluation of DBMS.]]></title>
            <link>https://medium.com/@gethikashalani/evaluation-of-dbms-6a2a8531b5b0?source=rss-28d9a1d6ceeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a2a8531b5b0</guid>
            <dc:creator><![CDATA[Geethika Shalani]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 12:15:47 GMT</pubDate>
            <atom:updated>2022-07-21T12:19:45.575Z</atom:updated>
            <content:encoded><![CDATA[<p>From pre-stage flat file system, to relational and object relational systems, database technology has gone through several generations and its history that is spread over more than 40 years now…</p><ul><li>Flat files (1960s — 1980s)</li><li>Hierarchical database (1970s — 1990s)</li><li>Network database (1970s — 1990s)</li><li>Relational database (1980s — present)</li><li>Object-oriented database (1990s — present)</li><li>Object-relational database (1990s — present)</li><li>Web enabled database(1990s — present)</li></ul><h4><strong><em>Flat files (1960s — 1980s)…</em></strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*DG3nmKZ6oNND-9C8Rjq1HA.jpeg" /></figure><p>Flat file database is a database that stores information in a single file or table. In a text file, every line contains one record where fields either have fixed length or they are separated by commas, whitespaces, tabs or any other character. In a flat file database, there is no structural relationship among the records and they cannot contain multiple tables as well.</p><p><strong><em>Advantages:</em></strong></p><ul><li>Flat file database is best for small databases.</li><li>It is easy to understand and implement. Fewer skills are required to handle a flat file database.</li><li>Less hardware and software skills are required to maintain a flat file database.</li></ul><p><strong><em>Disadvantages:</em></strong></p><ul><li>A flat file may contain fields which duplicate the data as there is no automation in flat files.</li><li>Flat file database waste the computer space by requiring it to keep the information on items that are logically cannot be available.</li><li>Information retrieving is very time consuming in a large database.</li></ul><p><strong><em>Implementation of a flat file database</em></strong></p><p>Flat file database is implemented in:</p><ul><li>Berkeley DB</li><li>SQLite</li><li>Mimesis</li></ul><h4><strong>Hierarchical database (1970s — 1990s)…</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*WwEbKwHqqHorfgVCh3jFfQ.png" /></figure><p>As the name indicates, hierarchical database contains data in a hierarchically-arranged data. More perceptively it can be visualized as a family tree where there is a parent and a child relationship. Each parent can have many children but one child can only have one parent i.e.; one-to-many relationship. Its hierarchical structure contains levels or segments which are equivalent to the file system’s record type. All attributes of a specific record are listed under the entity type.</p><p>In hierarchical database, the entity type is the main table, rows of a table represent the records and columns represent the attributes.</p><p><strong><em>Advantages:</em></strong></p><ul><li>In a hierarchical database pace of accessing the information is speedy due to the predefined paths.</li><li>The relationships among different entities are easy to understand.</li></ul><p><strong><em>Disadvantages:</em></strong></p><ul><li>Hierarchical database model lacks flexibility.</li><li>Maintenance and of data is inefficient in a hierarchical model.</li><li>This model is also inefficient for non-hierarchical accesses.</li></ul><h4><strong>Network database (1970s — 1990s)…</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/253/1*EK-EAzm8qck3Nh3VkbQz_g.jpeg" /></figure><p>Network database is basically a graph structure. The network database model was created to achieve three main objectives:</p><ul><li>To represent complex data relationships more effectively.</li><li>To improve the performance of the database.</li><li>To implement a database standard.</li></ul><p>In a network database a relationship is referred to as a set. Each set comprises of two types of records, an owner record which is same as parent type in hierarchical and a member record which is similar to the child type record in hierarchical database model.</p><p><strong><em>Advantages:</em></strong></p><ul><li>This model is conceptually easy to design.</li><li>This model ensures data integrity because no member can exist without an owner.</li><li>The network model also ensures the data independence because the application works independently of the data.</li></ul><p><strong><em>Disadvantages:</em></strong></p><ul><li>The model lacks structural independence which means that to bring any change in the database structure; the application program must also be modified before accessing the data.</li><li>A user friendly database management system cannot be established via network model.</li></ul><p><strong>Implementation of network database</strong></p><p>Network database is implemented in:</p><ul><li>Digital Equipment Corporation DBMS-10</li><li>Digital Equipment Corporation DBMS-20</li><li>RDM Embedded</li><li>Turbo IMAGE</li><li>Univac DMS-1100 etc.</li></ul><h4><strong>Relational database (1980s — present)…</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/1*WEGmOgu-liQ4G-U49tr1tQ.png" /></figure><p>Thus using relational database ample information can be stored using small tables. The accessing of data is also very efficient. The user only has to enter a query, and the application provides the user with the asked information.</p><p>Relational databases are established using a computer language, Structured Query Language (SQL). This language forms the basis of all the database applications available today, from Access to Oracle.</p><p><strong><em>Advantages:</em></strong></p><ul><li>Relational database supports mathematical set of operations like union, intersection, difference and Cartesian product.</li><li>Relational database uses normalization structure which helps to achieve data independence more easily.</li><li>Relational database uses a language which is easy and human readable.</li></ul><p><strong><em>Disadvantages:</em></strong></p><ul><li>The response to a query becomes time-consuming and inefficient if the number of tables between which the relationships are established increases.</li></ul><p>Implementation of Relational Database:</p><ul><li>Oracle</li><li>Microsoft</li><li>IBM</li><li>My SQL</li><li>PostgreSQL</li><li>SQLite</li></ul><h4><strong>Object-oriented database (1990s — present)…</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/261/1*_9cwSCDkzZDVCGmwBYMp5w.png" /></figure><p>Object oriented database management system is that database system in which the data or information is presented in the form of objects, much like in object-oriented programming language. Furthermore, object oriented DBMS also facilitate the user by offering transaction support, language for various queries, and indexing options.</p><p><strong><em>Advantages:</em></strong></p><ul><li>Navigation through the data is much easier.</li><li>Objects do not require assembly or disassembly hence saving the coding and execution time.</li></ul><p><strong><em>Disadvantages:</em></strong></p><ul><li>Lower efficiency level when data or relationships are simple.</li><li>Data can be accessible via specific language using a particular API which is not the case in relational databases.</li></ul><h4><strong>Object-relational database (1990s — present)…</strong></h4><p>Defined in simple terms, an object relational database management system displays a modified object-oriented user-display over the already implemented relational database management system. When various software interact with this modified-database management system, they will customarily operate in a manner such that the data is assumed to be saved as objects.</p><p><strong><em>Advantages:</em></strong></p><ul><li>Data remains encapsulated in object-relational database.</li><li>Concept of inheritance and polymorphism can also be implemented in this database.</li></ul><p><strong><em>Disadvantages:</em></strong></p><ul><li>Object relational database is complex.</li><li>Proponents of relational approach believe simplicity and purity of relational model are lost.</li><li>It is costly as well.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*xeCZzHhlQ4gFbG5PMeQDtg.png" /></figure><h4>Web enabled database(1990s — present)…</h4><p>Web enabled database simply put a database with a web-based interface.</p><p><strong><em>Advantages:</em></strong></p><ul><li>A web-enabled database allows users to get the information they need from a central repository on demand.</li><li>The database is easy and simple to use.</li><li>The data accessibility is easy via web-enabled database.</li></ul><p><strong><em>Disadvantages:</em></strong></p><ul><li>Main disadvantage is that it can be hacked easily.</li><li>Web enabled databases support the full range of DB operations, but in order to make them easy to use, they must be “dumped down”</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a2a8531b5b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[File System vs DBMS]]></title>
            <link>https://medium.com/@gethikashalani/file-system-vs-dbms-460950a05f50?source=rss-28d9a1d6ceeb------2</link>
            <guid isPermaLink="false">https://medium.com/p/460950a05f50</guid>
            <dc:creator><![CDATA[Geethika Shalani]]></dc:creator>
            <pubDate>Thu, 07 Jul 2022 10:56:53 GMT</pubDate>
            <atom:updated>2022-07-07T10:56:53.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*ALNOZ3R7Rp0CT_iyCZZMVw.jpeg" /></figure><p><strong>FILE SYSTEM…</strong></p><p><strong><em>What is a File System?</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*FfYWJZuO3LPTVYWAXO-8xg.jpeg" /></figure><p><strong>A file system is a software application that organizes and maintains files on a storage device</strong>. It manages the storage and retrieval of data. A database management system, or DBMS, is a software application that allows you to access, create, and manage databases.</p><p><strong><em>Features of the File System.</em></strong></p><ul><li>Space Management</li><li>Hierarchical Data Management</li><li>Metadata Management</li><li>Integrity Management</li><li>Restricting access to Files</li></ul><p><strong><em>Advantages of File System.</em></strong></p><ul><li><strong>Backup</strong>: Data held in files of computer-based systems can be backed up more quickly and automatically.</li><li><strong>Compactness</strong>: Data can be stored in a small amount of space.</li><li><strong>Data Retrieval</strong>: Computer-based systems offer improved data retrieval techniques that make it simple and efficient to retrieve data from files.</li><li><strong>Editing</strong>: Any information saved in computers in the form of files can be easily edited.</li><li><strong>File Sharing</strong>: Data saved in computer-based system files can be shared by several users at the same time.</li></ul><p><strong><em>Disadvantages of File System</em></strong></p><ul><li><strong>Data Redundancy</strong>: It’s possible that the same data is duplicated in many files. This results in data redundancy and memory waste.</li><li><strong>Data Inconsistency</strong>: Due to data redundancy, it’s probable that data won’t be consistent.</li><li><strong>Accessing Data Is Difficult</strong>: It’s not simple to get data out of a file management system. It isn’t as convenient as it should be.</li><li><strong>Limited Data Sharing</strong>: Data is dispersed across multiple files. Moreover, separate files may have different formats, and these files may be housed in several directories belonging to various departments.</li></ul><p><strong>DATABASE MANAGEMENT SYSTEM…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*pQbUoTKuWaQl34zzobDTSg.png" /></figure><p><strong><em>What is a Database Management System (DBMS)?</em></strong></p><p>manages databases (A database is a collection of interconnected data that is used to efficiently retrieve, insert, and delete data. It’s also used to arrange data into tables, schemas, views, and reports, among other things.)</p><p><strong><em>Types of Databases</em></strong></p><ul><li>Centralized Database</li><li>Distributed Database</li><li>Relational Database</li></ul><p><strong><em>Advantages of DBMS</em></strong></p><ul><li>Better Data Transfer</li><li>Better Data Security</li><li>Data inconsistency is minimized</li><li>Better decision-making</li><li>Increased end-user productivity</li><li>Faster data access</li></ul><p><strong><em>Disadvantages of DBMS</em></strong></p><ul><li>Staff Training Expenses</li><li>Data Migration Costs</li><li>Database System Maintenance</li><li>Performance</li></ul><p><strong><em>File System vs DBMS</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*KEYx-hIbeh1i7TNKPTALGQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=460950a05f50" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>