As we currently are in a steady state, we need to go a step forward by optimizing Oasis processes and escalating the project.
Working on Ocean would imply that we recreate Oasis infrastructure similarly the way we are using it in Masiv, meaning more costs and lack of data consistency due to both similar architectures (Oasis for Ocean and Masiv) being maintained by 2 different teams.
We are looking towards a transversal ecosystem to be the basis of all the current and incoming projects that allows us to grow in a controlled and organized way.
First, we need to evaluate if the current infrastructure is convenient and how it helps build the new Oasis approach proposal.
The following states a sketch of the current Oasis base costs.
ℹ️ This information consists of data from year 2022
Oasis base
Lambdas - USD
API Gateway has almost no costs
DynamoDB 12 USD
Cloudfront: no costs
S3 0,03 USD
Monolith
1200 USD
OSAs average
2USD
⚠️ For any change in infrastructure, we have to consider a maximum spend of 15 to 20 USD per month.
For more information about AWS prices and how are they calculated visit
Orchestrator Lambda builds the import.json in Orchestrator conf by using the data in DynamoDB, working as a switch of our OSAs.
The following states the current responsibilities of our Base libraries and which would be the desired changes to get them work transversely within our main products (Masiv, Ocean).