[Glass] How to start an eval of Gemsatone/S

charles at tradeblazer.com charles at tradeblazer.com
Tue Jan 18 08:28:16 PST 2022




Well , the need is arguably subjective 😊i.e. I may prefer a number of cooperating lightweight services sprawled in whatever topology I may wish,  we have currently for example microservices that handle stuff from smtp notifications i.e. even FIX integrations , trade data STP/ETL integrations which in turn push stuff thru MQ , where there’s persistence for monitoring, audit purposes and a myriad of scenarios. Bundling all that stuff into GS seems “uncomfortable” for one.


Now, of course, although my email was a bit verbose I was still summarizing.


There are scenarios where it would be perfectly fine for the UI to talk to a “specific” microservice which may indeed be running within Gemstone.

I gather from your reply that the way that works is indeed thru a “rest”-ish API and the fact that a web socket implementation exists is great.


Yet I would still have a similar need from a headless Pharo process and it would seem that probably the “standard” comm is via REST i.e. to Gemstone?

No local FFI supported semantics ? I guess that’s ok. 


BTW, I’m quite acquainted with Flutter and I do like it , i.e. mostly for what it delivers i.e. from one code base , its “pretty “ good at delivering multiple deployment outputs i.e. your desktop, web, iOS, android which look quite good.

However, Svelte is super fast but more importantly for me its data binding is so straightforward and clean that I can just RAD over it quicker, I’m looking also at using Svelte over Electron , and now there’s Tauri which seems interesting.


I’ll definitely look at your repo, it seems it may get me closer to where I want to go.




Charles A. Monteiro
Chief Technology Officer
Datasoft, Inc

Phone: 347-853-7349

Web:tradeblazer.com <http://www.tradeblazer.com> 


From: James Foster <smalltalk at jgfoster.net> 
Sent: Tuesday, January 18, 2022 10:49 AM
To: charles at tradeblazer.com
Cc: GLASS Mailing List <glass at lists.gemtalksystems.com>
Subject: Re: [Glass] How to start an eval of Gemsatone/S


Hi Charles,


Could you say a bit more about what role Pharo would take in this? I see that you describe “micro service(s) which in turn will talk to” GemStone. How thin is the Pharo layer? I understand that you don’t want something as heavy as Seaside, but I’m wondering if you would consider having the micro services hosted in GemStone so that you have only one Smalltalk layer. The reason I ask is because my current programming model is a SPA client using Flutter that makes calls to a GemStone API (I’ll have to look into Svelte!). The backend (https://github.com/jgfoster/WebGS) supports REST and WebSockets, so your front-end can be quite sophisticated and there is no need to have another layer.




On Jan 18, 2022, at 7:03 AM, Charles Monteiro via Glass <glass at lists.gemtalksystems.com <mailto:glass at lists.gemtalksystems.com> > wrote:


Hi all,


Not sure if this is the right spot to ask,let me know if not, this is more of sales evaluation i.e. that’s the intent.




I wish to evaluate Gemstone/S at first for some more tangential needs that are currently targeted for Mongo.

Our core product actually runs over Oracle and soon over any RDMS but for practical purposes we are targetting Postgres.

However, potentially the bigger need.


>From my FPL and Brooklyn Union Gas days I became quite familiar with using GemBuilder for VW however instead I want to engage Gemstone from Pharo and I understand that not to work the same way.


Recently , (yesterday) I discovered Sparkle which led me to discovering SparkleFFI , so there’s apparently some efforts under way to provide comm from Pharo to Gemstone i.e. more akin to Gembuilder/VW.


Anyhow, to cut to the chase.




I’m not interested in building a Seaside app that uses Gemstone for its persistence.

Rather, very thin , quite dumb Svelte/JS UIs will talk to Pharo microservice(s) which in turn will talk to Gemstone i.e. that’s the hope.


I would prefer some rpc mechanism where transaction boundaries are controlled from Pharo but I”ll be happy with whatever mechanism I can use to pass objects to Gemstone. 




1.	How do I talk to Gemstone from Pharo ? 

a.	I believe that Zinc can actually run on Gemstone so json/http(s) would be one way ? Any other way ? best way ?

2.	Is there a notification / push mechanism now in place e.g. change to a Gemstone collection could be notified to interested parties (Pharo)

a.	Is there a web socket implementation?
b.	Any other messaging implementation ? MQTT ? RabbitMQ etc ? 

3.	GemConnect / Postgres , would there be a separate additional license fee ?
4.	Has the performance of markForCollection changed much in all of these years i.e. does one have to allocate downtime ? i.e. what if the app actually needed to run 24x7, what are the accommodations for said scenario under current Gemstone/S.
5.	I assume that for development use that one can install Gemstone under WSL ? If so any issues to be aware of ?
6.	Sparkle is the new IDE ? but I see there’s also IoDE ? 


Finally , given all of the above , and never mind Gemstone/ S setup itself , is there some doc that illustrates a simple hello world scenario where a Pharo image is sending to Gemstone objects for persistence ? 

A cursory review of the Glass posts seem Seaside centric.


Thanks in advance, 




Charles A. Monteiro
Chief Technology Officer
Datasoft, Inc

Phone: 347-853-7349

Web:tradeblazer.com <http://www.tradeblazer.com/> 



Glass mailing list
 <mailto:Glass at lists.gemtalksystems.com> Glass at lists.gemtalksystems.com
 <https://lists.gemtalksystems.com/mailman/listinfo/glass> https://lists.gemtalksystems.com/mailman/listinfo/glass


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20220118/24c2e119/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8286 bytes
Desc: not available
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20220118/24c2e119/attachment-0001.png>

More information about the Glass mailing list