An in-house project would take a long time to develop most likely.
If you want to develop a large service providing project like an e-commerce site then you should read up on microservices if you haven't read up on them. Microservices basically split a lot of project logic into smaller components and workers usually that basically each are tasked with very specific things.
Netflix is a perfect example of microservices, where data is tracked throughout the whole application, there is a good caching layer, and everything is logged/meant to be restarted if it fails etc.
Building distributed services using finagle(from twitter), and hystrix(from netflix) as the start of the backend can be helpful as a start for relatively any project.
Ingesting large amounts of APIs can be done with a distributed architecture using several seperate akka clusters. This ends up being a bit more complex but there are good resources for this out there, some of which were developed for the company "fab" which has docs online like these: https://secure.trifork.com/dl/goto-berlin-2013/GOTO%20Night%... .
Even if you are developing something in-house odds are if you don't want to break the budget then you should find good parts that are already are working very well out there.
If you want more specifics, ask a more specific question though.
If you want to develop a large service providing project like an e-commerce site then you should read up on microservices if you haven't read up on them. Microservices basically split a lot of project logic into smaller components and workers usually that basically each are tasked with very specific things.
Netflix is a perfect example of microservices, where data is tracked throughout the whole application, there is a good caching layer, and everything is logged/meant to be restarted if it fails etc.
Building distributed services using finagle(from twitter), and hystrix(from netflix) as the start of the backend can be helpful as a start for relatively any project.
Ingesting large amounts of APIs can be done with a distributed architecture using several seperate akka clusters. This ends up being a bit more complex but there are good resources for this out there, some of which were developed for the company "fab" which has docs online like these: https://secure.trifork.com/dl/goto-berlin-2013/GOTO%20Night%... .
Even if you are developing something in-house odds are if you don't want to break the budget then you should find good parts that are already are working very well out there.
If you want more specifics, ask a more specific question though.