It’s no secret that IT modernization is a top priority for the US federal government. A quick trip in the congressional time machine to revisit 2017’s Modernizing Government Technology Act surfaces some of the most salient points regarding agencies’ challenges: In the private sector, excluding highly regulated industries like financial services, the migration to the public cloud was the answer to most IT modernization woes, especially those around data, analytics, and storage.
After working on a new feature or an improvement, it's normal that you want to deliver these changes to your users as fast as possible. Depending on your deployment pipeline, confidently deploying changes to production might include coordinating with whoever is leading on-call, getting their approval, manually deploying your changes, spending hours to monitor how it goes, and performing a rollback in case something goes wrong.
Businesses have been scaling rapidly in the cloud, driven by the pandemic and lured by the promise of agility and flexibility. But here’s a dirty little secret anyone who works in data knows. Despite the value of the cloud, tons of data hasn’t made it there. So, where is it? Spreadsheets. Still the stalwart workhorse, hero, and bane of the business world. We all love how Google revolutionized this world by bringing spreadsheets to the cloud.
The Apache Solr cluster is available in CDP Public Cloud, using the “Data exploration and analytics” data hub template. In this article we will investigate how to connect to the Solr REST API running in the Public Cloud, and highlight the performance impact of session cookie configurations when Apache Knox Gateway is used to proxy the traffic to Solr servers. Information in this blog post can be useful for engineers developing Apache Solr client applications.
