Nancy has arrived.
You may also enjoy:  Integrating Docker Solutions Into Your CI/CD Pipeline

Nancy is now wrapped up as a Docker image for execution in a pipeline or via an alias in a terminal.

Nancy is a tool to check for vulnerabilities in your Golang dependencies, powered by Sonatype OSS Index. docker-nancy wraps the nancy executable in a Docker image.

Source de l’article sur DZONE

The history, tools, and metrics of DevSecOps.

Where Did DevSecOps Come From?

Traditionally, software development involved two separate siloed departments: development and operations. The developers were responsible for writing the code and the operatives were responsible for implementing and managing it.

Back then, this software development process, which essentially followed the waterfall process, was simple and straightforward. Consumer demands were manageable, and if any changes or improvements were needed to be made, the operators could ping back to the developers to make the necessary amendments.

Source de l’article sur DZONE

Thinking of a master DevSecOps plan…

Whether it was the millions of users left vulnerable by Fortnite, or hackers gaining access to Dunkin’ customer accounts, 2019 has already seen some of the worst data breaches to date. To combat these types of attacks and vulnerabilities, organizations must be more cognizant of their security, and embrace a DevSecOps approach. And to do so, it is imperative that they provide the proper education and training for every facet of the organization.

You may also enjoy:  10 DevSecOps Implementation Principles

But it is important to note when educating organizations about security that some practices and technologies should be encouraged, while others should be avoided. These teachings need to be tailored for different audiences as needed, and new ways of learning and fitting into a DevSecOps scope should be explored in great detail.

Source de l’article sur DZONE

Spring Batch

In this post, we will show you how to use Spring Batch to read an XML file with your ItemReader using StaxEventItemReader and write its data to Oracle Database using Custom ItemWriter. We will also learn how to use ItemProcessor to process input data before writing to the database.

Custom ItemReader or ItemWriter is a class where we write our own way of reading or writing data. In Custom Reader we are required to handle the chunking logic as well. This comes in handy if our reading logic is complex and cannot be handled using Default ItemReader provided by spring.

Source de l’article sur DZONE

Imagine having an app where you can write and store your notes efficiently. Today, we are going to build an app that will keep track of your notes. We’ll use ASP.NET Core to build the app. We’ll also use .NET Core’s OAuth 2.0 authentication middleware to make sure the personal notes are kept secure.

My Private Notes App

As mentioned earlier, you’ll use an ASP.NET app to build your note-keeping app. Here’s how the app works: The home page will keep track of all your recent notes, and if you include more than three notes, the oldest will be shelved. Once we’ve built the app, you’ll learn how to secure it with OAuth. Read this starter project from GitHub to get started. 

Source de l’article sur DZONE

Check out the article below to become a master of Java Streams!

Declarative code (e.g. functional composition with Streams) provides superior code metrics in many cases. Code your way through this hands-on-lab article series and mature into a better Java programmer by becoming a Master of Java Streams.

The whole idea with Streams is to represent a pipeline through which data will flow and the pipeline’s functions operate on the data. This way, functional-style operations on Streams of elements can be expressed. This article is the first out of five where you will learn firsthand how to become a Master of Streams. We start with basic stream examples and progress with more complex tasks until you know how to connect standard Java Streams to databases in the Cloud.

Source de l’article sur DZONE

Recently I was looking for a way to implement access control for microservices. I needed a solution that would allow defining complex authorization rules that could be enforced across many services. After searching the web, I discovered a very promising Open Policy Agent project that seems to be the right tool for the job. In this series of three blog posts, I am going to introduce Open Policy Agent to you and highlight how it can help you.

What Is Open Policy Agent?

Open Policy Agent (OPA) is a policy engine that can be used to implement fine-grained access control for your application. For example, you can use OPA to implement authorization across microservices. However, there is much more that can be accomplished with OPA.

Source de l’article sur DZONE

Google autocomplete functionality

Whenever you start typing your search on Google, you get a list of recommendations, and the more letters you type, the more accurate the recommendations get. If you’re like me, you’ve always wondered how this works — is the inverted index being stored, or is it something else?

The data structure that would be apt here is a Trie.

Source de l’article sur DZONE

If you’re building custom applications owned by the same organization, there are many benefits of implementing single sign-on (SSO). You get shorter development time, increased security, and improved user experience. One of my favorite aspects of SSO is that instead of upgrading a large codebase all at once, you can do it a piece at a time.

What do I mean by that? Well, let’s say you’re looking to shift an app written in ASP.NET MVC 5 to ASP.NET Core MVC. You can do so by migrating each service at a time instead of rewriting the entire thing. You can then connect the two apps like they were one by enabling SSO. 

Source de l’article sur DZONE

Payara Server 5.193.1 is now Jakarta EE 8 Full Profile compatible!

We are very happy to report that we’ve successfully passed all of nearly 50,000 test suites of Jakarta EE 8 TCK, and Payara Server 5.193.1 is Jakarta EE 8 Full Profile compatible!

You may also like: Jakarta EE and Beyond!

The Payara team is extremely proud to be among the first to achieve Jakarta EE 8 Full Platform Compatibility, starting with Payara Platform 5.193.1. This is a significant milestone for Payara, and the team has done a huge amount of work to get this done. I think this is a great adoption story for Jakarta EE, in general, as Payara Server is not a Java EE 8 implementation. Furthermore, this shows that Jakarta EE is an open standard and can bring in new organizations and implementations.

Source de l’article sur DZONE