Keyhole Software successfully developed a scalable, user-friendly web application dashboard for traffic data solutions. Utilizing technologies like React, Node.js, GraphQL, and AWS, the team implemented features such as real-time analytics, secure authentication with Auth0, and seamless subscription management through Stripe. The project showcased Keyhole’s expertise in agile development, modern tech stacks, and delivering impactful, client-focused solutions. Project Overview A team …
Grand Rapids businesses trust Keyhole Software for expert software consulting and custom development services, tailored to meet the needs of diverse industries. Bring your ideas to life with Keyhole Software, the partner of choice in Grand Rapids for innovative software solutions. From healthcare and finance to entertainment and beyond, we’re here to help your business thrive with our client-focused approach and extensive industry expertise.Watch VideoLet’s TalkKeyhole Software’s Expertise Across IndustriesIn the fast-paced world of business, custom software solutions have become essential for improving processes and enriching user experiences. At Keyhole Software, we focus on delivering top-tier custom software solutions tailored…
Attention: This article was published over 2 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.Creating RESTful APIs with Spring Boot is a straightforward process, making it a popular choice for a variety of applications, from UI to batch …
In this post, I am going to demonstrate how to set up a simple Next.js web application. Next.js is a heavily opinionated JavaScript framework, in that it has a lot of conventions and recommended tools built into its design.
We’ll use Next.js version 14.2.2 to set up the groundwork for a simple web application. By “web application,” I mean an application that is designed primarily to collect input from a user in a web browser and return some output generated from that input.
In past blogs, I have discussed development containers (dev containers) in detail, from explaining their general mechanics to showing how they can bolster a team’s build automation. As a brief recap for the uninitiated: dev containers are a way of encapsulating a developer’s setup into a container, typically a Docker container. As a practical example, rather than forcing a new teammate to manually install and configure all the necessary tooling before contributing to a project, they can leverage a team’s devcontainer.json definition file to quickly spin up a fully configured development environment.
Microsoft has championed this workflow over the past few years, offering tight integration with tools like VS Code and Codespaces to make containerized development as seamless as possible. At the time of writing, the developer experience has reached a point where I honestly prefer to operate within a dev container for certain types of projects. When I open a team’s codebase within VS Code and it informs me that they have provided a dev container to use, I have higher confidence that I’ll be using the same versions of their tools and seeing the behaviors that they expect.
I’ve even come to trust these setups more than an equivalent set of Dockerfiles or docker-compose scripts, just because the simplicity of the ecosystem makes it more likely that everything is well-maintained and configured correctly. It’s easy to see how these standardization and automation benefits can be a huge boost to teams…once they’ve adopted the right tools to integrate with them.
But what if you don’t want to use VS Code?