React is a tool that constantly evolves, influencing web development's evolution in the process. Here are six libraries that can help solve everyday tasks and change the way you develop with React.
Four years ago, Devbridge adopted Scrum as a process for driving development. However, we're constantly reevaluating our processes to ensure they produce the best, most efficient products possible. In this post, one of our senior software engineers shares some things he's learned in those four years. These ideas can help build better backlogs and engage development teams. To not just build products, but own them.
Touchscreen devices have changed how we interact with computers. People are already spending more time on their smartphones than their desktop machines. This shift in behavior has prompted the need for mobile-first design and development. A mobile-first approach is important, but where do you start? In this post, we detail three being methods used today and what approach will work best for you.
Sass (syntactically awesome stylesheets) is a powerful tool that helps users write CSS with ease. In this post, I explore the more advanced possibilities of Sass, and detail seven techniques to help developers write more efficient code.
With the sheer amount of software being created today, software development techniques are rapidly and continuously evolving. Even industries that previously had a very fixed cycle, such as car manufacturers, are moving towards continuous delivery. As more companies adopt an Agile development process to support continuous delivery, testing (or quality assurance) and delivery need to keep pace. Hence, the rise of DevOps, which manages the entire product lifecycle. But, there are varying levels of DevOps. In this post, we define those levels and share with you our approach. How does your enterprise measure up?
An often overshadowed aspect of building great products is ensuring these products are reliable and perform as expected. Similar to physical products, the quality of a digital product has a large impact on the customer/user experience. Typically, a quality assurance (QA) or testing team leads this effort. But, what is the difference between QA and testing, and does it matter? We believe so, and so should you.
As mentioned in my previous post, A path to microservices, adopting a microservices architecture is not simple. It requires many prerequisites to be managed successfully. With multiple services you quickly realize how many resources they use. Even the smallest service has a run-time footprint and consumes CPU cycles, even when sitting idle. Multiply this by number of services and you quickly get the picture. This post explores how this can be improved, and if it is possible to go beyond microservices to a serverless architecture.
Developers today most likely can’t imagine not having source control and continuous integration systems. However, one area enterprises may still be struggling with is how to integrate an automated test solution for native mobile applications into a continuous integration workflow. This article provides suggestions on how to do so along with an example of how we did it at Devbridge Group.
If you are a software developer, you already know what Node.js is. You know how to create an API and may feel like Superman while implementing new features. However, as you attract more users, response time gets slower, and with workloads increasing, your application may start to fail. For those with existing applications, this article explores the most likely issues and how message queues, specifically with RabbitMQ in Node.js, effectively helps applications connect and scale. For others planning to build a new application, I incorporate useful tips to help you avoid issues up front.
There are many benefits that a microservices architecture brings if implemented correctly. However, there are many parts involved that should be taken into consideration before going down the path of adopting a microservices architecture environment. This post delves into the details and highlights several areas to consider to ensure any organization has a successful plan in place.
Today, nearly every webpage contains some kind of infographic. Infographics are a nice design feature, but also help readers understand and digest content easier. There are several options for dealing with sets of images/icons. Yet from a front end developer's perspective, we prefer SVG graphics, which have become widely supported on all modern browsers and are in vector graphics format, making them easily scalable on different screen resolutions among other advantages. Our latest post looks at three different approaches.
In an unprecedented era of high customer expectations, low market confidence and the constant threat of small and nimble players disrupting the market, financial institutions find themselves in a position where they must evolve or become extinct. As established players continue to be dependent on legacy technology and monolithic systems that require significant overhead and lead time to deliver even the smallest increment of value, many are struggling to satisfy the needs of their customers and shareholders and their ability to remain competitive is diminishing. This post explores how financial services institutions, particularly banks, can effectively evaluate and embrace the microservices architecture movement.