Articles

Unfortunately, it is not disaster recovery, high availability, or cloud technologies that are inherently difficult to understand, but rather the action of implementing them for software applications that is difficult. The unique method of implementation for a microservices architecture is explored. Regulatory compliance doesn’t stop just because an effective disaster recovery requirement is tough to satisfy for infrastructure unique to sleek microservices. The high-availability location transparency bliss offered by a cloud solution is appealing to a security engineering department. However, the headache starts when the technology presents a handful of undesirable surprises that leak RESTful microservices to the outside world. These are the challenges that post-SOA cloud-resident robustly scalable applications will need to address and overcome. The goal is to explore several popular methods of accomplishing these tough objectives so that engineers can further research the most practical solution. An innovative implementation that leverages Service Bus relays as an elegant disaster recovery solution while enforcing a strict subnet where RESTful microservices solely live will be discussed. The curiosity lies in the atypical experimentation beyond basic gateways and the facility of using such simplicity while still answering day-to-day software development infrastructure challenges for applications we build. Resilient full-service web proxy service crashes and delivery latency switches by harnessing the microservices pod health will also be discussed [1].

The study aimed to examine the availability of protective clothing and its usage among workers at the University of Cape Coast in the central region of Ghana. It used the Accident-Proneness Theory and the Theory of Reasoned Action to achieve the study's objectives. The study adopted the positivist research paradigm. The study used a descriptive design with mixed methods. The study population comprised all workers and supervisors whose work demands the use of protective clothing at the University of Cape Coast. The study used multistage sampling techniques (stratified, purposive, proportional and Systematic random sampling techniques) to select one hundred and ninety-six departmental workers and five (5) supervisors in the University. The main instruments for data collection were a Semi-structured questionnaire and an unstructured interview guide. Mean and standard deviation, frequency count, and percentages were used to analyse the quantitative data. The qualitative data was analysed through the development of data categories and themes. The study concluded that “not all the protective clothing for the various departments were available. The University ensured that workers used what was in stock at the department. The protective clothing supplied to the various departments was insufficient, so their continuous use of the existing ones got them defaced, bringing about shortages. The study also revealed that workers used protective clothing most often, but not all used it because safety laws were relaxed. The study recommended that the University ensure a regular and adequate supply of PPC, insist on its usage, and enforce the use of PPC by all workers whose work demands it.

Smallholder farmers face challenges when they lack information on their agricultural activities. To address this, we suggest a web-based system that can be used by farmers to help them in decision making considering the fact that all necessary information is provided by the system. Farmers can input crop type they want to grow and area. This data will help to recommend them the best crops that are suitable to be grown in that area and the necessary growing practices that can be done to produce high yield and have maximum profits, considering the average rainfall of that year. A persistent issue we face in Zimbabwe is the lack of access to reliable agricultural data. In the agricultural sector, one major uncertainty for farmers is the outlook of their future harvest. Once their produce is ready for sale, the presence of other potential buyers compels traders to offer prices that align closely with those in the formal market. However, without timely information, traders can take advantage of the situation by purchasing crops at unfairly low rates. Having data that tracks prices across various markets in near real-time would enable farmers to have a precise and complete understanding of their selling choices to maximize their profits.

The control of processes is made smooth and effective by Programmable Logic Controllers (PLCs), which are essential to industrial automation. The assessment of PLCs' reliability is crucial since more and more sectors depend on them for crucial tasks. In-depth reviews of the components necessary to evaluate PLC system reliability are presented in this study. To ensure a robust review, the review first clarifies the basic concepts of reliability, highlighting the significance of system uptime and the ramifications of failures in industrial settings. Next, it examined the different elements that go into a PLC's overall reliability, such as availability, testability, and (maintenance and maintainability). The percentage of the reviewed papers that employed (maintenance and maintainability), testability, or availability to improve the reliability of PLC systems showed that, availability and (maintenance and maintainability) has been employed the most for enhancing system reliability, accounting for 32% each of publications analyzed, followed by testability, accounting for 28% respectively. The scatter chart that depicts the progression of reliability components from 2010 to 2023 also explained that the use of availability and (maintenance and maintainability) was increasing. This upward trend can be explained by the fact that repairable systems are heavily reliant on availability, whereas (maintenance and maintainability) tend to avoid unnecessary equipment breakdown and testability, which ensures the ease with which the functionality of any system or component can be ascertained with the required level of precision.

Modern organizations leverage highly distributed, global deployments to provide high availability and resiliency for cloud-first applications. By hosting these applications across multiple geographic locations and relying on highly available services, organizations can prevent disruption to their business and reduce complexity by employing the scale of infrastructure offered by major cloud providers. Global deployments in the cloud are built on well-known models such as failover, load balancing, and scalability. However, traditional methods used to recover from regional failure—while effective—can be complex. Typical multi-region recovery and high availability system architectures have latency and cost risks that should be considered when facing other limitations such as deployment models in the cloud. This document describes the different traffic management techniques that can be applied to multi-region strategies, focusing on trade-offs and costs. The introduction of new traffic management techniques being applied to the traditional global architectures now allows organizations to adopt cloud services more efficiently. Traffic management is much more straightforward in some environments, while others have started to leverage their traffic management platform via routing. In multi-region deployments, active-active and active-passive are the most common architectural models, allowing organizations to seamlessly handle failover, scalability, and global distribution based on business goals and requirements. However, traffic management for these infrastructures is critical to ensure just data distribution and efficiency, maintaining costs under control and workloads rerouted when necessary. Using the new traffic management techniques will allow organizations to evolve system architectures easily based on business requirements, taking advantage of cost benefits from multiple infrastructures. In these scenarios, traffic management becomes a crucial backbone of success to ensure that traffic is being efficiently and intelligently distributed [1].

The last few years have seen an increased adoption of cloud infrastructure, which has in turn led to a growth in large-scale distributed architectures in data centers to accommodate cloud resource elasticity and resiliency better. Selecting the right approach to build secure, scalable, and reliable cloud infrastructure within a budget is always a challenge. This text focuses on offering practical solutions for designing and building a secure, scalable, and reliable cloud-based infrastructure where auto-scaling and multi-region deployments are the two key approaches to offer high availability. It covers designing secure and scalable microservices using cloud platforms. The content will provide an understanding of public cloud architecture, the design of microservices running on the cloud, and also the design patterns used in the cloud era. With real-world examples, you will learn how microservices can enable scalable distributed systems. Furthermore, you will be walked through multi-region deployments, auto-scaling, and traffic management in cloud environments, using a sample environment setup and useful tips and tricks for monitoring. Finally, you will see a mock implementation of cloud infrastructure on-premise for a private cloud or single-node cloud. By the end of this text, you will be able to build, manage, and deploy a highly scalable and reliable cloud-ready solution [1].