September 26, 2018
TABLE OF CONTENTS
Senior Engineering Consultant
Samantha is an experienced, AWS-certified cloud architect at Levvel, where she has worked with application development, cloud enablement, and architecture assessment efforts for a variety of clients. She has over five years of experience in technical strategy and delivery for clients ranging from startup to Fortune 500 companies. Samantha specializes in serverless machine intelligence and virtualized resources, and enjoys writing (technical and otherwise) in her free time. She has a B.S. in Computer Science and a B.A. in Spanish from the University of Virginia.
Tyler is a Engineering Consultant at Levvel with several years of web application development and delivery practice, primarily for small startup companies. His experience with various backend technologies motivates him further to learn about different types of architectural design. Tyler holds a B.S. in Computer Science from Southern Illinois University.
Douglas has more than 10 years of experience in software development at companies ranging from startups to a top Fortune 500. He specializes in node.js and front-end technologies such as Angular, React, and Vue. In his free time, he enjoys learning new technologies, contributing to open source projects, and spending time with his wife and two miniature dachshunds, Ranger and Roxy. He has a B.S. in Management Information Systems from The University of Alabama.
At the end of lunch with a mentee, I used the items on our table to express the fundamental concepts of Kubernetes. Sometime after explaining the purpose of the Kubernetes scheduler, she asked a question I spent the next several weeks thinking about.
API design is crucial, giving structure to application interaction. Given cross-functional teams and applications, development time is reduced with a clear, intuitive way to access data. API development often follows two approaches: REST and GraphQL.
As of June 2018, the state of California passed a new privacy law that could lead to more consequences for US-based companies than the European Union’s General Data Protection Regulation (GDPR). Here's what you need to know and how to be compliant.
Before your data scientists wring value out of your reams of data, it has to be accessible and, on some basic level, coherently arranged. To harness all that brainpower, you need to keep the data wrangling to a minimum. Enter the data lake.