Have you heard about Agile Architecture practices or about how adaptive methods can help us create solutions iteratively without the Big Up-Front Design?
Agile Integration arises among these scenarios of constant innovation, where solutions need to be published in ever-smaller development cycles and meet the business needs and the expected time-to-market. We can say that Agile Integration practices are among the main catalysts for accelerating companies’ digital transformation journeys.
AWS is known to be a high-performance, scalable computing infrastructure, which more and more organizations are adapting to modernize their IT. However, one must be aware that no system is secure enough to ensure business continuity! Hence, you must have some kind of plan in place for your disaster recovery. With this article, we aim to discuss the top three disaster recovery (DR) scenarios that show the use of AWS:
Amazon Web Services (AWS) enables you to operate each of these three examples of DR strategies in a cost-effective manner. However, it’s also essential to note that these are only examples of potential approaches. Variations and combinations of these are also possible.
While we have a lot of blogs for various complex Integration scenarios and methods using MuleSoft, a few of my friends asked me to write something more basic, step-by-step process to get started with the MuleSoft Anypoint Studio and start integration using this amazing tool.
Are you familiar with any of the following scenarios?
Instead, we should be doing substantial work at the right time so that both you and humankind are benefitted from your work. The question is, how.
With the rise of Single-Page Applications (SPA) in web frontends, it is often the case that backend REST APIs based on Zato need to be configured for CORS. This article will explore what CORS is and how to make Zato participate in scenarios using it.
CORS, as an acronym, has several parts:
PDF documents are small-sized, highly secure files. Almost all businesses use PDFs for processing their files. The reason being a distinguishing feature of maintaining format regardless of the tool used to access PDF files. It’s no surprise that all our invoices, official documents, contractual documents, boarding pass, bank statements, etc. are usually in PDF format.
Even as developers, we come across scenarios when a PDF file needs to be verified or used to locate certain parts of data. You can either do this manually given that you have loads of time to spare or you opt for automation testing. When it comes to handling tricky components of such files using automation, it might seem a bit too tricky. But that’s not the case. Selenium test automation can make it really easy to test PDF file formats.
If there are top ten buzzwords in the technology industry in the year 2019, the container is sure to be one of them. With the popularity of Docker, more and more scenarios are using Docker in the front-end field. This article shows how do we use Docker in the visualization interface of Nebula Graph, a distributed open-source graph database.
Docker is widely used in daily front-end development. Nebula Graph Studio (A visualization tool for Nebula Graph) uses Docker based on the following considerations:
With the Auto Scale for VPC, you can create an instance group to scale according to your requirements. Based on the target utilization metrics that you define, the instance group can dynamically add or remove instances to achieve your specified instance availability.
Let’s start with a quick one, as an introduction to VPC.
