Software Engineering Week 6

      This week I learned more about Service Oriented Architecture (SOA) and how it can improve efficiency amongst large teams. In the initial design of our web servers, our system was monolithic. We had web servers for our front end and backend, and had a single database that was controlled by the backend. However this week we switched to SOA, allowing us to split up the two web servers, effectively making them microservices, and ran a independent databases on each. By doing this it was much more efficient for our team to work when split up, only requiring all hands when doing system testing. One important part of making our microservices communicate effectively was the use of message queues, specifically RabbitMQ. With message queues, each of the microservices could communicate with each other and keep track of changes in each database as well as track requests needing to be handled. One interesting thing I learned about RabbitMQ was the different methods in which messages can be sent to various subscribers. While orchestration is straight forward it can be less efficient, requiring changes to the service sending the messages when a subscriber needs to be added or deleted  The other method, choreography, seems much better. Utilizing an exchange, this method does fanout meaning the service sending the message only has to send the message once, and the exchange can be configured to determine which subscribers can receive the message. The use of an exchange seems to be much more preferable as it offers a single point to configure subscribers, and prevents having to make code changes to the sending service.

Comments

Post a Comment

Popular posts from this blog

Software Engineering Week 4

    The most interesting thing I have learned about in my reading of "Software Engineering at Google" are how each of the various processes are executed. While I am familiar with most of the processes I've read about so far, including code reviews, unit testing and system testing, the manners in which these are executed at Google are different from how they have been executed in my professional experience. For code reviews in particular, Google engineers ensure they invite various other software engineers to fill the roles of correctness and comprehension checking, language readability checking, and code owner. However, in my experiences this is not explicitly required. While a single engineer on the team often fills a couple of these roles, there wasn't an engineer specifically dedicated to carry out each of these tasks. Another interesting thing I learned was a recommendation about the use of the "sleep()" function in testing. While sometimes waiting is re...
Read more

Capstone Project Week 10

   What did you accomplish this week? This week I looked into integrating the stac-browser container within the docker compose YAML file provided in the stac-fastapi-pgstac project. In addition I cleaned up some unnecessary data included in STAC items written by our parser as well as read further documentation from the National Hurricane Center on how I can do additional parsing on dropsonde remark messages. I also published a build and tested docker image including our team's parsing tools to docker hub to allow it to be pulled from our AWS instance. What is your plan for next week? Next week I will work with my team to get our STAC Server running and hosted within an AWS server for demonstration and testing with our stakeholders.  What challenges, if any, are you currently facing in project development? Do you need instructor assistance?  So far local development has been smooth on a Windows 11 operating system. Containers are able to be built and ran using docker...
Read more

Capstone Project Week 11

What did you accomplish this week? This week I pushed updates to our parser development branch which included additional parsing for remarks and removal of certain metadata properties that were unnecessary for describing the who, what, when, and where of a dropsonde message. In addition I was able to get our parser, STAC API, and STAC browser containers running and hosted AWS, load our STAC database with STAC items using our custom API endpoint integrated with our parser, and test our application's availability on the internet. After confirming our application's accessibility, I scheduled a demonstration with our mentor to show our progress and attain feedback. What is your plan for next week? Next week I will demonstrate our STAC parsing and catalog browsing capabilities within our container hosted on AWS to our project mentor.   What challenges, if any, are you currently facing in project development? Do you need instructor assistance?  I'm not facing any challenges at...
Read more