This article will set up a basic Spring Boot app that incorporates Apache Camel to move some sample files around.
If you are like me, you find that flat-file processing can be pretty dry. Considering what Apache Camel does, its name is very fitting. While there are plenty of reasons for the name, it definitely makes sense that Apache Camel does a lot of lugging things around for you…
Several years ago, 2012 to be precise, I wrote an article on an approach to unit testing Spring Batch Jobs. My editors tell me that I still get new readers of the post every day, so it is time to revisit and update the approach to a more modern standard.
The approach used in the original post was purely testing the individual pieces containing any business logic. Back then, we didnโt have some of the mocking capabilities that we have today, so I went with an approach that made sense at the time.
However, there have been a few improvements in the past several years. One of those improvements has been the ability to Mock beans within a Spring Context. Thatโs where the @MockBean annotation comes to the rescue.
AWS SQS (Simple Queue Service) can provide developers with flexibility and scalability when building microservice application(s). In this quick start tutorial, we will demonstrate how to configure a FIFO queue for a fictional online marketplace.
What Is A FIFO Queue?
A FIFO (first in, first out) queue is used when the order of items or events is critical, or where duplicates items in the queue are not permitted. For example:
– Prevent a user from buying an item that isn’t available on a marketplace.
So you have mastered Spring Boot and started toying around with React. Now you want React to talk to your Boot app as your back-end API. Thatโs fabulous. You probably already know how to do this, but there is a kicker. You want to package them and start both of them as just one project.
Well, youโre in luck! This blog is going to take a couple of simple projects and combine them into one project. Lace up your boots and get ready to React!
Under an aggressive 6-week deadline, a four-person Keyhole Software Consulting team was charged with delivering functionality to the first phase of a capital asset planning application for an international engineering consulting firm.
Deliverables included ensuring all UI controls displayed properly on mobile devices, application functionality in offline mode, and seamless integration with the working application.