The Chariot Blog
Tutorials, analyses, and the business of software — our consultants share over two decades of knowledge.
AI Is Writing Code. But Who's Responsible for What It Gets Wrong?
Chariot Solutions in 2025: AI, Modernization, and the Evolving Role of Technologists
Event Recap: What Does It Mean to Be a Developer in the Age of AI Agents?
Philadelphia’s Healthtech Moment: Chariot’s Tracey Welson-Rossman Calls for a New Era of Collaboration
Adding Conversational AI to Your App — Part 3: The UX of Chat Interfaces: What We Gain and Lose
Adding Conversational AI to Your App — Part 2: Adding Conversation History to the Context
Adding Conversational AI to Your App — Part 1: Converting Natural Language into JSON Actions
Migrating Java Applications to Kubernetes
Unleashing AI in Marketing: Key Insights from Slice Communications & Chariot Solutions Webinar
Populating a Data Lake with AWS Database Migration Service and Amazon Data Firehose
Data lakes are great for holding large volumes of data, such as clickstream logs. But such data has limited usefulness unless you can combine it with data from your transactional, line-of-business databases. And this is where things get tricky. Simple approaches, such as replicating entire tables, don’t scale. Streaming approaches that include updates and deletes require logic to determine the latest value (or existence!) of any given row. All of which has to be translated into static data files in a data lake. In this post I look at one approach to solve this problem: AWS Data Migration Service to capture changes from the source database and write them to a Kinesis Data Stream, and Amazon Data Firehose to load those records into Iceberg tables.
Notes on a Hobby Project, or a Foray into HTMX
Automate the Boring Stuff with AI
Navigating Social Sweepstakes 2025: Insights & Strategies from Matt Kaufman
Populating Iceberg Tables with Amazon Data Firehose
In this post I look at using an Amazon Data Firehose to populate Iceberg tables, with the automatic optimization features that AWS announced in November 2024.
HealthTech Data Infrastructure Trends
What’s the point of Lambda SnapStart?
Lambda SnapStart is intended to improve the cold start time for a Lambda function. It’s been available for Java workloads since 2022, and was recently released for Python and .Net workloads. It works by running the initialization code of your Lambda function when you release a version, and then storing an image of the Lambda execution environment. Cold starts load this image rather than running the initialization themselves. Given that cold starts happen unpredictably, and may be measured in seconds, this seems like a win-win situation. The reality, as usual, is more nuanced. SnapStart introduces its own cold start delays, as it loads the image into the runtime. And it increases the time and effort of deployment. In this post I drill down into the nuance, so that you can decide whether it’s a worthwhile choice fo your project.
Troubleshooting ECS Deployments
At Chariot, we’re fans of deploying on Amazon’s Elastic Container Service using Fargate. However, there are a few stumbling blocks for ECS deployments. In this post I cover the common problems that I’ve seen, and some of the techniques that I use to avoid tripping over them.
Chariot Day Recap 2024
SBRA Briefing Writeup
Ready to transform your business?
We solve complex business problems with technology. Let's discuss how we can help you build, modernize, and grow.
Start A Conversation