{{announcement.body}}
{{announcement.title}}

New(er) Application Journey

DZone 's Guide to

New(er) Application Journey

See how this developer gets the most ROI for AWS.

· Web Dev Zone ·
Free Resource

robot-made-of-amazin-boxes-in-tree

A little over a year ago, I started a series called, "New Application Journey," which was focused on replacing a legacy application for my mother-in-law's small business in the southeast portion of the United States.  I used her business needs to create a new application from scratch using Angular, MySQL, and the AWS environment. I documented my approach and findings in a series published on DZone.

Technology Approach

For the original journey, I utilized the following frameworks:

On the service side, I chose the following options:

The application utilizes AWS as follows:

You may also like: Gitting Started With Git.

A Year Later

Now that a year has passed ... and the one-year free trial of the AWS service is over ... monthly charges have started to appear for the AWS usage of her application. 

The cost has not been significant in any way. In fact, what AWS is charging for the value being provided is actually an amazing deal when all things are considered.  

However, I thought it would be nice to create a follow-up series to focus on the following topics:

  • Analysis of Cloud-Based Charges.

  • Seeking Alternatives to AWS.

  • Cost-saving Methods for Cloud-Based Services.

  • Implementing A Serverless Approach.

  • Looking At The Commission Report With Fresh Eyes.

  • Retrospective Part Two: What Is Now Known.

While the application being discussed is very small in nature, my hope is that the information provided will be applicable to services on a larger scale.

Stay tuned as this series will be kicked off in November. 

In the meantime, if you want to read (or hopefully re-read) the original series, the articles are noted below:

Have a really great day!

Topics:
web design & development ,aws ,spring boot ,angular ,elastic beanstalk

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}