Hi Ian, I'm preparing a GSoC 2026 proposal for In-browser packaging of AsterixDB and wanted to introduce myself briefly.
I am a high school graduate with a strong Java backend background, having hands-on experience building concurrent systems, HTTP-based services, and full Jakarta EE applications (TaskEE). I’ve also worked on multithreaded processing systems (Divipix). Over the last couple of days, I’ve focused on getting up to speed with AsterixDB itself: - I have built AsterixDB locally and successfully run the sample cluster and Admin Console. - I Studied the SQL++ primer and have started tracing the runtime flow. - I explored the packaging layer (asterix-podman) and compared it with the older Docker-based setup One thing that stood out to me is the shift from the older multi-process container setup (CC + multiple NCs via supervisord) to the newer simplified startup path using asterixccnc. That seems especially relevant for the in-browser packaging direction, since a browser environment will likely require a much more minimal, single-node execution model rather than full cluster orchestration. Now, I am focusing on understanding the HTTP API and tracing the execution path. I had a few focused questions where your guidance would help me align early: - Is the current asterixccnc-based startup path the most relevant entry point to think from for browser packaging, or are there other runtime modules that would be more appropriate? - Are there any starter contributions I can make that would best demonstrate fit for this project before the proposal deadline? I want to make sure my proposal is both relevant and targeted. Your feedback or suggestions on my current approach would be really helpful. Thank you for your time. Best Regards, Adan Ali.
