The month of September marks the busiest buying season for the federal government. In the final month of fiscal year 2018, an astonishing $97 billion was spent on 509, 828 contracts. On average, this equates to $3.2 billion per day.
September is also getting busier and busier. Between 2015 and 2018 spending increased by 39%.
Federal agencies are using multiple public clouds in addition to on-premises private and non-cloud infrastructures. This mutli-cloud adoption is creating increasingly complex environments and making it difficult to manage and protect data. Without proper data management, hybrid and multi-cloud environments can quickly become just another series of expensive and risky silos. All cloud migration strategies should encompass data management best practices to maximize cloud adoption benefits while minimizing risk.
The Obama and Trump administrations may not have a lot in common. But encouraging federal agencies to move their computing workloads to cloud services providers has been a definite point of policy continuity.
Recall that during the Obama years, cloud and a fresh data center consolidation initiative roughly coincided. (I say “fresh” because of presidential findings that the government has too many computers dated at least to the Reagan administration).
Cloud adoption among government agencies is reaching an inflection point. Driven by the cloud’s cost-efficiencies and ability to offer an improved citizen experience, faster delivery of mission capabilities, agile development, and scale applications up and down, much of the initial reticence about cloud models is dissipating.
Congress first enacted federal appropriations law in 1809. It’s kept lawyers, contractors, and judges busy ever since. A question arising in many sellers’ minds at this time of year is, what money is available for contracts in more than one fiscal year?
Ransomware is quickly becoming the favored means for criminals to extract a profit from unsuspecting villains – most notably in the public sector. Throughout 2017 ransomware grabbed the headlines – WannaCry, Petya, etc. – both of which targeted government agencies. When they succeed the implications can be serious.
Are you thinking of moving your databases to the cloud? Perhaps, you’re thinking about transitioning to database-as-a-service (DBaaS)? But what’s involved? What hurdles must be overcome and how do you chart a path to cloud migration of your most sensitive workloads?
Why Move Databases to the Cloud?
Migrating to the cloud offers several benefits to public sector database administrators (DBAs).
Government shutdowns are a costly business. The 2013 shutdown cost $24 billion in lost economic output while the 1996 shutdown resulted in $2.1 billion in government costs. We are yet to learn the impact, if any, of the three-day 2018 shutdown.
But, what we do know is that shutdowns are not universal. For many critical government employees, the lights never go out. Here’s just a shortlist:
Veterans Affairs (VA) remained operational.
Shutdown, sequestration, budget cuts. With challenges like these, how can government agencies even attempt to build and sustain an engaging workplace where employees are satisfied, productive, committed and, let’s face it, less likely to leave.
Government websites can’t afford downtime. Even if they aren’t losing revenue because of un-scheduled outages, latency, DNS attacks and so on, the public loss of access to resources and employee loss of productivity is frustrating and stressful, as well as a public relations nightmare.
It’s also a big distraction for IT operations.