Skip to main content

Finally uploading to S3 using java sdk

One of the reasons I joined my employer was that I would get some experience with AWS and S3. But so far the ride is a roller coaster ride and I have been working on something totally different and first we created our own S3 like system and then uploading to S3 and AWS was handled by another rockstar friend in the team :).  Now it almost seems like I wont get a chance to work on it so I was like let me anyway write a simple program, so I signed up for AWS and tried this. Its a simple thing and took me only 2-3 hours but its worth spending it because for past 3 weeks I am working on cleaning technical debt accumulated over years and that doesnt give that much joy. Doing this give me some joy.

On that note one of the team mate shared this today to me

http://www.businessinsider.com/syndromes-drive-coders-crazy-2014-3



public class S3StorageService {
    private static final AppLogger logger = AppLogger.getLogger(S3StorageService.class);
    private String bucketName;
    private String accessId;
    private String secretKey;
    private String tempFolder;

    @Override
    public String uploadObject(String guid, InputStream in) {
        File file = getTempStoragePath(guid);
        try {
            saveToTempFile(in, file);
            String key = getObjectKey(guid);
            AmazonS3 s3Client = getS3Client();
            s3Client.putObject(new PutObjectRequest(bucketName, key, file));
            return key;
        } finally {
            FileUtils.deleteQuietly(file);
        }
    }
    private File getTempStoragePath(String guid) {
        File baseDir = new File(tempFolder);
        File hashedPath = new File(new File(new File(baseDir, guid.substring(0, 2)), guid.substring(2, 4)),
                guid.substring(4, 6));
        hashedPath.mkdirs();
        return new File(hashedPath, guid);
    }
    @Override
    public void deleteObject(String guid) {

        String key = getObjectKey(guid);
        AmazonS3 s3Client = getS3Client();
        s3Client.deleteObject(new DeleteObjectRequest(bucketName, key));
    }

    @Override
    public void downloadObject(String guid, OutputStream out) throws StorageServiceException {
        String key = getObjectKey(guid);
        AmazonS3 s3Client = getS3Client();
        S3Object object = s3Client.getObject(new GetObjectRequest(bucketName, key));
        InputStream objectData = null;
        try {
            objectData = object.getObjectContent();
            IOUtils.copy(objectData, out);
        } catch (IOException e) {
            throw new StorageServiceException(e);
        } finally {
            StreamUtils.closeQuietly(objectData);
        }
    }
    private String getObjectKey(String guid) {
        return  "Files/" + guid;
    }

    private AmazonS3 getS3Client() {
        AWSCredentials awsCredentials = new BasicAWSCredentials(accessId, secretKey);
        AmazonS3 s3Client = new AmazonS3Client(awsCredentials);
        return s3Client;
    }
}

Comments

Popular posts from this blog

Killing a particular Tomcat thread

Update: This JSP does not work on a thread that is inside some native code.  On many occasions I had a thread stuck in JNI code and it wont work. Also in some cases thread.stop can cause jvm to hang. According to javadocs " This method is inherently unsafe. Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked". I have used it only in some rare occasions where I wanted to avoid a system shutdown and in some cases we ended up doing system shutdown as jvm was hung so I had a 70-80% success with it.   -------------------------------------------------------------------------------------------------------------------------- We had an interesting requirement. A tomcat thread that was spawned from an ExecutorService ThreadPool had gone Rogue and was causing lots of disk churning issues. We cant bring down the production server as that would involve downtime. Killing this thread was harmless but how to kill it, t

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it can happe

Preparing for an interview after being employed 11 years at a startup

I would say I didn't prepared a hell lot but  I did 2 hours in night every day and every weekend around 8 hours for 2-3 months. I did 20-30 leetcode medium problems from this list https://leetcode.com/explore/interview/card/top-interview-questions-medium/.  I watched the first 12 videos of Lecture Videos | Introduction to Algorithms | Electrical Engineering and Computer Science | MIT OpenCourseWare I did this course https://www.educative.io/courses/grokking-the-system-design-interview I researched on topics from https://www.educative.io/courses/java-multithreading-for-senior-engineering-interviews and leetcode had around 10 multithreading questions so I did those I watched some 10-20 videos from this channel https://www.youtube.com/channel/UCn1XnDWhsLS5URXTi5wtFTA