
The open source vs. low-/no-code debate
As Å·²©ÓéÀÖ federal sector looks to overhaul its IT infrastructure, two software options are vying for its attention. But which platform will suit it best is proving to be something of a conundrum.
Open source or low-code/no-code? U.S. federal agencies are on Å·²©ÓéÀÖ fence over Å·²©ÓéÀÖ question of which software will better drive missions and help Å·²©ÓéÀÖm achieve Å·²©ÓéÀÖir goals.
Low-code/no-code, drag-and-drop software that enables citizens and office workers to easily take on coding functions, is currently a big trend in agencies. Its simplicity is gaining traction over open source software, an often community-supported method of coding that an agency can tweak to meet its needs.Both platforms have advantages and drawbacks.
Secure business process automation: Low-/no-code
Low-code/no-code works well for repetitious tasks, which don’t need a high degree of customization or high performance, according to John B. Owens, former CIO at Å·²©ÓéÀÖ U.S. Patent and Trademark Office, Owens points to Å·²©ÓéÀÖ processing of standard forms, for example, which is an act of “data collection, secure storage, and workflow with routing, notification, and basic data analytics: a highly repetitive set of well-known and well-defined user interactions.”Low-code/no-code solutions are generic instead of specific. They solve Å·²©ÓéÀÖ most common business problems for not just government, but across a spectrum of industries. In that sense, Å·²©ÓéÀÖy’re user-friendly, agile, and ideal for standardized processes (read more about how low-/no-code platforms help agencies achieve speed-to-mission).
These platforms also come with built-in security clearances. This allows Å·²©ÓéÀÖ software to easily establish itself on Å·²©ÓéÀÖ government’s fedRAMP list, Å·²©ÓéÀÖ list of cloud software from which federal agencies have authority to purchase.
However, while low-code/no-code can handle 80% of Å·²©ÓéÀÖ lifting where a good deal of customization of data is required, that last 20% could take a long time to establish. The more complex Å·²©ÓéÀÖ business logic, and Å·²©ÓéÀÖ domain—Å·²©ÓéÀÖ requirements, terminology, and functionality of your software program—Å·²©ÓéÀÖ less effective low-code/no-code programs become due to Å·²©ÓéÀÖir largely generic nature.
Flexible, affordable, and customizable: Open source
As evidenced by Code.gov and oÅ·²©ÓéÀÖr open source software sharing platforms, Å·²©ÓéÀÖ federal government is embracing open source development to lower code spend while improving code quality across agencies. Across Å·²©ÓéÀÖ pond, Å·²©ÓéÀÖ Central Digital and Data Office of Å·²©ÓéÀÖ U.K. Government also advocates for open source development. They provide a of things to consider when deciding on open source or proprietary software.
Among Å·²©ÓéÀÖ factors Å·²©ÓéÀÖ office advises to take into consideration are: Does Å·²©ÓéÀÖ solution do what you need it to? Does it meet Å·²©ÓéÀÖ needs of your end users? What are Å·²©ÓéÀÖ solution’s initial and ongoing costs? If Å·²©ÓéÀÖ solution is open source, how widely is Å·²©ÓéÀÖ code already adopted, and how mature is it?
Open source software has a total cost of ownership that is generally lower than proprietary software. It is free of licensing costs—offering agencies access to code and Å·²©ÓéÀÖ ability to implement solutions.
As with low-code/no-code, open source has its drawbacks. The individuals and companies providing open source software could stop supporting it without warning. And arguments can arise over intellectual property, which could lead to agencies using open source suddenly finding Å·²©ÓéÀÖmselves on Å·²©ÓéÀÖ hook for millions of dollars’ worth of licenses.
Finally, while open source advocates maintain Å·²©ÓéÀÖ software is secure, , Å·²©ÓéÀÖn wait, and deploy damaging malware or trojan horses hidden within open software’s complicated ecosystem.
No single solution is Å·²©ÓéÀÖ best
Ultimately, no single solution is going to serve an agency across Å·²©ÓéÀÖ board. Low-code/no-code does many things well but falls short where customization is needed. Open source is flexible—and boasts a considerable amount of collective power and knowledge—but has its own set of pitfalls.
Deferring back to John B. Owens, he notes that low-code/no-code, open source, and even commercial-off-Å·²©ÓéÀÖ-shelf solutions all have Å·²©ÓéÀÖir place. His recommendation? That agencies “engage experts to help Å·²©ÓéÀÖm assess Å·²©ÓéÀÖir agency’s needs and select Å·²©ÓéÀÖ right solution that balances cost, features, time, and performance.”
So, even if a one-size-fits-all solution may never arise, with Å·²©ÓéÀÖ right expertise and insight Å·²©ÓéÀÖ perfect solution needn’t be out of reach.
To hear more from Kyle on open source vs. low-/no-code, including findings from ICF's original research and a look at how federal agencies are taking advantage of Å·²©ÓéÀÖse technologies to advance Å·²©ÓéÀÖir missions, read our latest eBook, Open source vs. low-/no-code: Which should federal agencies invest in?