Codetown

Codetown ::: a software developer's community

We might have to store Social Security Numbers.  We REALLY don't want to do this in our own database, we'd like some external 'vault' service that stores them encrypted and getting to them is difficult.  Does anyone have any ideas along these lines?

Views: 81

Reply to This

Replies to This Discussion

Kevin, I've seen many solutions ranging from encryption to cloud storage. I'm curious: have you come up with some good ideas?

Reply to Discussion

RSS

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

There's also a free Java Jobs mailing list. It's a Yahoo group so you have to create a Yahoo account to use it.

 

Enjoy the site? Support Codetown with your donation.



Reading List

Designing Microservice Architectures the Right Way: Michael Bryzek's Lessons Learned at QCon NY

At QCon New York 2018, Michael Bryzek discussed how to design microservice architectures “the right way”. Key takeaways included: engineers should design schema first for all APIs and events, as this allows the automated code generation of boilerplate code; and investment should be made in automation, such as deployment and dependency management.

By Daniel Bryant

Why Segment Returned to a Monolith From Microservices

Alexandra Noonan, from Segment, describes how they moved their original monolithic architecture to microservices and then found problems with that approach which required them to rethink and move back to a (different) monolithic architecture with far more appreciable benefits.

By Mark Little

© 2018   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service