Modern businesses are highly consumer-driven. Delivering value to our customers should, therefore, be our first priority. Making the tasks of our customers more convenient and efficient should be our primary goal. To do that, we need ways to figure out “what” exactly makes our customers more efficient and brings them convenience in their tasks. 

This requires a lot of trial and error. This requires us to build and experiment with systems and features to see if these capabilities actually bring significant value to our customers. This is the primary motivation that drives enterprise architecture to be much more disaggregated and composeable. Heard about “Microservices” anyone? 

Source de l’article sur DZONE

A few months back, I was going through some posts related to Test Automation in Quora. Suddenly a question posted by an anonymous user caught my attention – “What is Maven in Selenium?”

This was not the first time I came across this question or similar questions during my journey as an SDET. This is quite common since there is a lot of confusion regarding the differences between the build automation tools (“Maven” is one of them), and the test automation libraries, mostly among the testers who have just started learning/working on test automation and came across build tools for the first time.

Source de l’article sur DZONE

A few weeks ago I had some interesting debates on the projects I work on, on questions like:

  • Is the automation engineer a developer?
  • Is a developer the best candidate to be an automation engineer? 
  • Where does the good ol’ Software Engineer in Test (SET, a.k.a SDET) fit in this fierce new world full of code and dependencies? 

It seems that the trend nowadays when looking for job candidates in automation is that they need to have the skills of a programmer. I have been doing technical interviews for people who are running for Test Engineer positions for years, and this trend has been increasing more and more. That is why I give the same advice to anyone asking me how to get into the automation world: “Start learning the fundamental concepts of object-oriented programming and how they apply to automation testing.”

Source de l’article sur DZONE

Spider is a storage engine for the MariaDB Platform that allows you to build distributed databases from a standard MariaDB setup. The technology is not complicated, although the implementation is. This blog will explain how the Spider storage engine works, what it does and will also show some of the use cases.

MariaDB Storage Engines

Before we look at the Spider storage engine, let’s have a quick look at the storage engine concept. A storage engine is the implementation of code that manages the low level of data access in MariaDB. The storage engine handles things such as reading and writing data, row-level locking, if supported, multi-versioning and transaction management, among other things.

Source de l’article sur DZONE

This article was first published on the MQTT.Cool blog.

Most MQTT brokers currently available on the market provide native support for WebSockets, thus enabling any MQTT JavaScript library to establish communications by encapsulating MQTT messages into WebSocket frames: This is called the MQTT Over WebSocket

Source de l’article sur DZONE

In today’s fast-paced software world, quick delivery of the product is often not an option but a necessity. Building software also requires a high level of flexibility in responding to the constantly changing market trends and customers’ demands. The problem is that with traditional project management, a quick change of plans inevitably leads to higher costs or longer project duration. Luckily there are agile methods that allow us to avoid such pitfalls. This refers not only to software development but also to testing processes.

What Is Agile Testing?

Agile in software development is an approach that focuses on the people performing their work and their cooperation aimed at delivering the right product to the customer. It is an iterative development process that creates requirements through constant collaboration between the client and cross-functional self-organizing teams. Agile testing is a practice that follows the rules of agile development and helps create solutions tailored to customer needs.

Source de l’article sur DZONE

HTTPS is a secure version of HTTP designed to provide Transport Layer Security (TLS) [the successor to Secure Sockets Layer (SSL)], the padlock icon in the address bar that establishes an encrypted connection between a web server and a browser. HTTPS encrypts every data packet to transmit in a secure way and protects sensitive data from an eavesdropper or hacker.

You can implement HTTPS by installing the SSL certificates on your web application. You can use either certificate issued by trusted Certificate Authorities (CA) or Self-Signed Certificate.

Source de l’article sur DZONE

Google is heavily investing its resources in AI and machine learning research intending to shell out products and services for the future. So whether it has to do with computational photography or email suggestion features, Google has always been active on this front. Recently, Google also launched the famed “Google Recorder”. You might wonder that there are several voice recorder apps in the market so why this? But we all know it, if it is from Google it has to be a contender for the top slot! 

Before we explore further, let us see whether Google reads the race or not! And, yes we see right there that Google has done a great job when it comes to AI-based research and launches. 

Source de l’article sur DZONE

Different applications need different permissions. Although you might have a single resource server providing data to multiple apps, it’s often the case that you don’t want all users of application A to access application B. 

In this tutorial, you’ll learn how to use Okta and Spring Boot to implement SSO with two client applications and a single resource server. You’ll also learn how to restrict access to the resource server based on app scores and how to use access policies to enforce authentication and authorization rules.

Source de l’article sur DZONE

Implementing high-availability capabilities for SAP ERP systems can be a complex undertaking. But the importance of high availability in keeping companies “open for business” can’t be overstated. Applications and servers will fail. Power outages will occur, and a natural disaster may strike at any time. 

This article provides technical guidance on two key steps in the process to implement high availability for SAP ERP systems: 

Source de l’article sur DZONE