InfoQ Homepage Source Code Content on InfoQ
-
/articles/transforming-legacy-healthcare-systems/en/smallimage/transforming-legacy-healthcare-logo-small-1731055590401.jpg)
Transforming Legacy Healthcare Systems: a Journey to Cloud-Native Architecture
Discover how Livi navigated the complexities of transitioning MJog, a legacy healthcare system, to a cloud-native architecture, sharing valuable insights for successful tech modernization. Our experience illustrates that transitioning from legacy systems to cloud-based microservices is not a one-time project, but an ongoing journey.
-
/articles/how-to-use-multiple-github-accounts/en/smallimage/how-to-use-multiple-git-accounts-small-1714116220419.jpg)
How to Use Multiple GitHub Accounts
Git is a popular tool for version control in software development. It is not uncommon to use multiple Git accounts. Correctly configuring and switching Git accounts is challenging. In this article, we show what Git provides for account configuration, its limitations, and the solution to switch accounts automatically based on a project parent directory location.
-
/articles/enterprise-github-actions/en/smallimage/lessons-learned-from-enterprise-usage-github-actions-small-1672998170003.jpg)
Lessons Learned from Enterprise Usage of GitHub Actions
GitHub Actions is an effective CI tool. However, integrating it into enterprise organizations can be challenging. This article looks at best practices for GitHub Actions in the enterprise.
-
/articles/moldable-development/en/smallimage/logo-1663947983331.jpg)
Moldable Development: Guiding Technical Decisions without Reading Code
Developers spend most of their time reading code. Moldable Development challenges reading as a means to gather information from the system, by creating custom tools that show the problem in a way that makes it comfortable to understand. The solution typically follows quickly afterward. Glamorous Toolkit is a moldable development environment designed to decrease the cost of custom tools.
-
/articles/mvp-mva-legacy/en/smallimage/logo-1660735098327.jpg)
Chipping Away at the Monolith: Applying MVPs and MVAs to Legacy Applications
Legacy applications actually benefit the most from concepts like a Minimum Viable Product (MVP) and its related Minimum Viable Architecture (MVA). Once you realize that every release is an experiment in value in which the release either improves the value that customers experience or doesn’t, you realize that every release, even one of a legacy application, can be thought of in terms of an MVP.
-
/articles/iac-configuration-drift/en/smallimage/logo-1659715903797.jpg)
Infrastructure as a Code—Why Drift Management Is Not Enough
The reality is that configuration drift will remain unavoidable for the foreseeable future. An EaaS solution, coupled with an IaC platform and good change management policies will help you prevent drift and shorten your development cycles.
-
/articles/Standardized-Specification-Driven-API-Lifecycle/en/smallimage/logo-1647025459155.jpg)
A Standardized, Specification-Driven API Lifecycle
At QCon Plus last November, Kin Lane, Chief Evangelist with Postman, and the Open Technologies Team lead presented on API specifications. API specifications are essential to him and at Postman. So he wanted to share a bit of how they see API specifications impacting how they produce and consume APIs.
-
/articles/communicating-engineering-work-business/en/smallimage/logo-1643971643396.jpg)
Talking Like a Suit - Communicating the Importance of Engineering Work in Business Terms
This article explores how to construct engineering work as a story, including clearly presenting a problem, offering a solution, and showing the business a path to success that solves their problem and avoids failure. By presenting your case in this way, you significantly increase your chances of getting these engineering problems addressed, while also becoming a better partner for the business.
-
/articles/upgrading-legacy-solutions/en/smallimage/5-things-to-remember-when-upgrading-your-legacy-solution-small-1636369934577.jpg)
Five Things to Remember When Upgrading Your Legacy Solution
Legacy software is still employed, even though it frequently fails to meet critical demands and core business operations. By choosing the right modernization strategy and software development teams, you can easily cut down on high legacy software maintenance costs and increase productivity.
-
/articles/github-monolith-microservices/en/smallimage/gitHub-journey-from-monolith-to-microservices-small-image-1627307383403.jpg)
GitHub’s Journey from Monolith to Microservices
This article explores GitHub's recent journey towards a microservices architecture. It takes a deeper look at GitHub’s historical and current state, goes over some internal and external factors, and discusses practical consideration points in how Github tackled their migration, including key concepts and best practices of implementing microservices architecture.
-
/articles/series-debt-guide-agile-journey-2/en/smallimage/Technical Debt-s-1623850162647.jpg)
‘Debt’ as a Guide on the Agile Journey: Technical Debt
In this article in a series on how ‘debt’ can be used to guide an agile journey, we will provide two examples of smells that are related to technical debt, explain the symptoms, the impact on the business and in our organization, outline the experiments (countermeasures) that we have introduced in an effort to try to remove the smell, and provide some specific advice for you to be inspired.
-
/articles/software-engineering-google/en/smallimage/software-engineering-google-s-1622200397846.jpg)
Software Engineering at Google: Practices, Tools, Values, and Culture
The book Software Engineering at Google provides insights into the practices and tools used at Google to develop and maintain software with respect to time, scale, and the tradeoffs that all engineers make in development. It also explores the engineering values and the culture that’s based on them, emphasizing the main differences between programming and software engineering.