David Sietz

Privacy by Design is rapidly becoming the new focus for go forward architecture and application design. However, few companies have the luxury of building out new solutions and are struggling with ways to adapt their current systems to meet Privacy by Design criteria. If you find yourself in such a situation, know that you're not alone.

In this session we'll review some common legacy designs and provided suggestions for them that you can implement to better align your systems toward privacy strategies.

Agenda

• Privacy Strategies
• Monolithic Databases
• Batch Processing
• SOA
• Next Steps

Github Repo

Open source is growing with leaps and bounds. Even corporations are adopting the open source products and reaping the numerous benefits. But there’s more than the products that need to be adopted – the Open Source Model itself is also highly valuable.

Find out how adopting the Open Source Model can improve your organization’s “time to market”, product quality, professional climate, and Agile adoption. We’ll focus on what constitutes an Open Source mindset, how to implement it, and some of the pitfalls and anti-patterns to avoid.

Agenda

• defining ownership
• open source contribution models
• implementing open source in the enterprise
• pitfalls & anti-patterns

Github Repo

Should Information Management systems apply the services architecture? Many data provisioning and BI systems are monolithic, tightly coupled, difficult to scale, and stumble when it comes to delivering MVP in a timely manner.

In this session we will look at the common obstacles such systems inherently bring with them, and how the Data as a Service architecture pattern addresses many of these issues.

Agenda

• setting expectations
• anti-patterns
• DaaS pattern
• using a business lens

In 2020, 61% of businesses migrated their workload to the cloud. Many of us were part of (or have been part of) such migrations. Unfortunately, most of these migration were performed without first building a substructure. Such a pitfall is now coming back to haunt us and proving difficult to resolve.

So what are some of those designs used in the substructure, and how can they be implemented as frameworks in an ephemeral environment?

Join us as we explore the patterns and show how they can be implemented using AWS services.

Agenda

• Accounts, Networking, & Security
• Treating it “as Code”
• Shared Services
• MACH Architecture with Lambda & Kafka
• Building a DaaS PaaS
• next steps

Business requirements are not the only influencers of our technical solutions. Laws and Regulations transform the technical landscape in ways that require us to redefine our architecture, as well as our skill-set. This is especially true with Data Privacy. Since GDPR and CCPA, our industry is witnessing a new career path emerge: the Privacy Engineer. Where security started 10 years ago, so does privacy engineering. Join us as we look at Privacy by Design (PbD) and introduce some architecture patterns that align with privacy strategies.

Agenda:

• Overview
• Data Usage Agreements
• Data Tracker Chain
• Data Privacy Inspector
• Data Security Guard
• Forward Thinking

There are numerous jobs in our industry and we all have an understanding of what those roles entail. But there is a new role that has emerged. It is the elusive role of the Privacy Engineer. ​

This is the Jackalope of our professional community: seldom seen, hard to explain and has the traits of other professions mixed into one. But does it exist? And if it does exist, what would that profession look like? Not to mention, how would we start on this professional path?​

Accompany me as I look at what influenced the need for Privacy Engineering, other professions that followed this same evolutionary journey and where the profession is headed.

There are numerous jobs in our industry and we all have an understanding of what those roles entail. But there is a new role that has emerged. It is the elusive role of the Privacy Engineer. ​

This is the Jackalope of our professional community: seldom seen, hard to explain and has the traits of other professions mixed into one. But does it exist? And if it does exist, what would that profession look like? Not to mention, how would we start on this professional path?​

Accompany me as I look at what influenced the need for Privacy Engineering, other professions that followed this same evolutionary journey and where the profession is headed.

Over the last decade, our profession has adjusted to the business's drive to enhance collaboration and adopt a more customer-centric focus. In response, we've implemented agile frameworks and redesigned our applications to utilize machine learning to provide a more customized experience. As a result, we've decreased our “Time to Market” and our “Time to Point of Sale”.

But if you feel there's still something missing, you're not alone.

​While traveling to and from the airport for ArchConf 2021, I was reminded of some vital practices by my shuttle drivers. Their behavior opened my eyes to what was missing from my professional approach. As Brené Brown said, “Authenticity is the daily practice of letting go of who we think we're supposed to be and embracing who we are.” ​

Join me as a share what I've learned during those hours of travel, and how it has redefined my strategy with the business and the customer experience.