Force 3 Copyright 2018

About This Tech Talk

Despite the urgency of IT modernization and the federal government's Cloud Smart policy, most federal agencies unfortunately still find themselves lagging when it comes to cloud migration and adoption. While cloud migration is a massive endeavor, it doesn’t have to be unmanageable, let alone impossible.

Indeed, a lot of the hassle and potential complications can be mitigated, if not altogether avoided, by developing a comprehensive strategy for migrating mission critical applications to the cloud. In this session we will discuss important best practices you should consider before moving any mission critical applications to the cloud. In addition, we will discuss a “Bridge to the Cloud” strategy which utilizes containers and automation to provide the flexibility needed to adopt a multi cloud provider approach. This will be an interactive session with live demonstrations on application selection and prioritization, application performance baselining, and containerized applications running in both private and public cloud environments.

Charles leads a team of software engineers who provide innovative IT solutions to federal customers in the defense, intelligence, and civilian spaces. Before joining Force 3 in 2016, Charles spent 15 years at IBM. Most recently, he was the director of technical sales for the Mid- Atlantic Region, where he led a 200+ person organization of software architects and specialists.


Charles Fullwood

Senior Director, Software Solutions

Register for This Training
Date: Wednesday, Jan. 23, 2019
Duration: 10 AM - 2 PM

Location: 2151 Priest Bridge Drive, Crofton, MD 21114 


Upcoming Tech Talks

The Importance of Application Performance to the Mission
February 20 2019
Automating Security Response
March 20 2019
Intent Based Networking
April 24 2019

Overcoming the Challenges
of Cloud Migration

Wednesday, January 23, 2019 | 10 AM - 2 PM

Force 3 HQ | 2151 Priest Bridge Drive, Crofton MD 21114

Friday, January 23, 2019 
10 AM - 2 PM


Fix the following errors: