It’s important to thoroughly consider both the benefits and drawbacks of microservices architecture before you implement it. It’s also important to implement robust testing strategies to ensure the reliability and quality of the overall system.
Over the course of this blog, I’ll explore the good, the bad, and the testing side of microservices. My hope is that this will give you a starting point as you consider whether microservices architecture is right for your project.
Over the course of this blog, I will be focusing on using Bloom Filters in Java development. We’ll briefly talk through what they are and why they’re handy, and then we’ll dive into a hypothetical use case and tutorial.
As a note, this post is just meant to get you started on the track to using a Bloom Filter in the wild. What we discuss here will stay high-level but will give you a general idea of how it would work on a project.
Without further ado, let’s get started.
Recently, I’ve worked on automating some internal processes for building and releasing Flutter applications. Part of this effort included utilizing Fastlane with a Continuous Integration/Delivery platform to build and deploy the app. This blog post will outline the process I followed to run the build on CircleCI after I had configured Fastlane to build and deploy the application from my local machine.
In the post, I’ll be talking more about the map() function – how it differs from other common loops, exploring its optional second parameter, using mapping in the return statement, and tracking with keys. By the end, I hope you’ll have a clearer understanding of how the map() function can be useful in your React projects.
Please note, this post is geared toward React beginners and new coders. Veteran users may not glean as much from the content.
Recently, I worked on automating some internal processes for building and releasing Flutter applications. Part of this work has involved integrating integration test runs and screenshots as part of the release and deployment process.
I wanted to be able to use the same set of tests to validate our code on Android and iOS devices without having to write large amounts of platform-specific code or configuration. These tests needed to be able to integrate with Fastlane, so they can be utilized by CI/CD. Specifically, this restricted setup runs using command line tools with no manual steps in Xcode or Android Studio, aside project level configuration.
This blog is Part 2 of a three-part series exploring automating Flutter CI/CD on CircleCI. Part 1 covered setting up Fastlane to build and deploy applications locally, this post outlines automating screenshot capture and test runs, and part 3 discusses configuring CircleCI to automate these processes.